Touchscreen Responsiveness? - Galaxy Tab 2 Q&A, Help & Troubleshooting

Hey guys, I'm having a small issue with my tab that's beginning to drive me crazy.
I'm not sure if it was present right out of the box as I wasn't completely stock for more than 30 minutes. After I flashed metallice's kernel for stock I noticed some issues a few hours later that every now and then pinch to zoom on the tab became extremely tedious. Like I'd move my fingers half way across the tab and it would barely zoom in.
Scrolling around the page was still smooth, but pinch to zoom was very "hitchy"
I flashed CM9 afterwards and stuck with the stock cm kernel thinking something Metallice did in the kernel wasn't reacting well with my tab, but nope still happened.
After 4.0.4 came out for the tab I flashed back to stock using odin and updated via ota. Everything seemed fine for a few hours and then the issue came back.
It's still occurring on Jelly Bean but it's not quite as pronounced. Just wondering if anyone else has run into this issue and if anyone has a possible fix.
Thanks,
Will

Related

[Q] Enabling GPS causes random reboots

Hey guys, tried a search but couldn't find anything. I am running a rooted stock 2.3.3 with faux kernel and for the longest time I had GPS disabled without knowing it (what can I say, I'm good with directions). I recently enabled it and have been getting reboots at random times while it is on. I turned it off today and have not had a crash yet, so I assume this is the problem.
Has anyone had or fixed this? I have thought about installing the weapon ROM, seems to get a lot of positive reviews for stability which is most important to me. If there is an easy fix though, I'd rather just stay put on my current setup.
Thanks!
It did the SOD thing last night when I was sleeping (had GPS off the whole day) so I figured something was buggy and wiped it to install weapon. Hopefully it works out *crosses fingers*.

[Q] Random reboots and activation issues

I've been scouring this site for similar problems, I found one thread that sounded similar but no one responded to it...
I've been running CM10 and CM10.1 on my phone since I've had it, a little over a year. Last weekend I updated to the newest nightly with the CM updater like I always have. As far as I could tell, everything worked normally.
That afternoon, the phone rebooted a few times on its own after it froze up. It slowly got worse, and now its to the point where it will not stay running for longer than about 2-3 minutes on any CM10 based rom. Additionally, on boot up, when it gets to the home screen, the message, "no sim card detected" shows up for a few seconds until 4g connects. Then, when I unlock the screen it takes me to the activation screen which seems to go nowhere. If I press the home button, it will take me back to the home screen and the phone will work like it should until it reboots.
On Monday, reinstalled the stock touchwiz rom and that seemed to make everything better. I haven't noticed any random reboots or the sim card message thing. So today, I tried CM10.1 again. Same issues. I also tried Carbon and PacMam - both resulted in the same issues.
So....I seem to have a functioning phone on touchwiz, which is good...but I really don't like touchwiz. I'd really like to be running carbon, but a hard reboot every 3 minutes is unacceptable. Obviously, this can't be a software thing - everything was fine until a week ago. Could a dying SIM card cause this?
Same thing here,,,, I can not install any 422 rom... and I notice it will not see my Ext-SD card.
Ive been getting that same activation issues as well, are you rebooting the phone in an area with poor reception?
Some 4.2.2 ROMs do not seem to have this issue, ParanoidAndroid, and ParanoidKANGDroid are two i can think of.
eyerawnick said:
Ive been getting that same activation issues as well, are you rebooting the phone in an area with poor reception?
Some 4.2.2 ROMs do not seem to have this issue, ParanoidAndroid, and ParanoidKANGDroid are two i can think of.
Click to expand...
Click to collapse
Yeah, signal is strong. Something like -89dB. I'll try paranoid android this afternoon.
Try liquidsmooth ... I had many reboot issues with carbon and a few other roms but none when it comes to liquidsmooth (recommend 4-16 nightly) and ktoonz 4-11 kernel ... perfect match ... if issues continue there im out of options good luck

[Q] Display Failure 1 Month after flashing CM 10.1 - any ideas as to the cause?

Hi Everyone,
I bought an S3 at the end of May, rooted and flashed cm 10.1 about a week later (and flashed firmware required to get the camera working a few days after that).
Earlier this week, the display suddenly shifted green and started to die - no amount of resetting, wiping, or unrooting and flashing stock would fix it (the screen ultimately came back on, but with a permanent blue-green tint and low resolution). Although I've basically chalked it up to a hardware failure (maybe gpu?), I got a replacement and am a little hesitant to flash CM again for fear that this might be a common issue.
Has anyone here experienced something similar? Is there any way that flashing and running a custom rom for a month could put undue stress on the motherboard, gpu, or other hardware? Would a custom kernel address the issue?
Just basically looking for thoughts from people who are way more experienced with this stuff than I am. Sorry if this has been posted before; I browsed the forums briefly and the display issues I saw didn't quite seem to match what I experienced.
purudaya said:
Hi Everyone,
I bought an S3 at the end of May, rooted and flashed cm 10.1 about a week later (and flashed firmware required to get the camera working a few days after that).
Earlier this week, the display suddenly shifted green and started to die - no amount of resetting, wiping, or unrooting and flashing stock would fix it (the screen ultimately came back on, but with a permanent blue-green tint and low resolution). Although I've basically chalked it up to a hardware failure (maybe gpu?), I got a replacement and am a little hesitant to flash CM again for fear that this might be a common issue.
Has anyone here experienced something similar? Is there any way that flashing and running a custom rom for a month could put undue stress on the motherboard, gpu, or other hardware? Would a custom kernel address the issue?
Just basically looking for thoughts from people who are way more experienced with this stuff than I am. Sorry if this has been posted before; I browsed the forums briefly and the display issues I saw didn't quite seem to match what I experienced.
Click to expand...
Click to collapse
A co-worker of mine had an S3 T999 on tmobile that did this same exact thing on the stock unrooted rom. I'd say its unrelated to CM, and glad you got a replacement. It should not do it again, so CM is safe to run on it.
Not a Rom issue. Sounds like just bad luck of the draw. I am on my 3rd or 4th s3 and i haven't had a Rom kill my phone yet.
Sent from my GT-P5113 using xda premium

Aging or a software problem?

My Note 10.1 is extremely slow recently. I mean it can work normally for half an hour and then hang for a minute or not allow me to turn the screen on for 30 or more seconds. Is this because of age? Is the flash inside degraded to a point it slows everything down or maybe clear new ROM will fix this? I am asking because I am not exactly sure I will be able to load a new ROM on it (the recovery is a bit broken, but it will probably be possible through Odin). If it is happening to other old, heavily used Note 10.1's I will just leave it as it is, instead of risking of breaking it completely. So, how are your good old Note 10.1's behaving lately?
One replace battery if you think thats at fault .
Two wipe and install stock rom via Odin .
Nand / flash should not degrade in such a short time .
It took me a while, since I use the tablet very rarely and have gotten used to it's slow downs but I have solved the problem - it was caused by the kernel it had. Changing the kernel to a new, stable one solved the issue. The tablet is still a bit slow, but no longer hangs for 30 seconds like it used too. Thanks everyone for help.
Magnesus said:
My Note 10.1 is extremely slow recently. I mean it can work normally for half an hour and then hang for a minute or not allow me to turn the screen on for 30 or more seconds. Is this because of age? Is the flash inside degraded to a point it slows everything down or maybe clear new ROM will fix this? I am asking because I am not exactly sure I will be able to load a new ROM on it (the recovery is a bit broken, but it will probably be possible through Odin). If it is happening to other old, heavily used Note 10.1's I will just leave it as it is, instead of risking of breaking it completely. So, how are your good old Note 10.1's behaving lately?
Click to expand...
Click to collapse
I experienced the same problem until recently with my GT-n-8010, when it still was under the official 4.4.2 firmware. I also thought about an age problem, but it was definitely not. I've been trying for the last four days the CM13 BETA developped by senior member Lirokoa - everything is explained in this thread : http://forum.xda-developers.com/galaxy-note-10-1/development/rom-lollipop-t3269375 - and it's just as if I had gotten a brand new device, so it really was a software problem, not a hardware one. I advise you to try it too, you should not regret it

Ghost touches?

Anyone else getting ghost touches? It started after 4 months for me. I enabled visible touches and occasionally my device will just start spamming taps everywhere.
I'm going to RMA it, just got to install stock rom first.
Installed stock and RMA'd, they replaced the display and now thr phone is on its way back.
Apparently not re-locking was a good choice, no one cared.
Hey bro, what did u do to fix your problem? Im facing the same issue on Android 11
Replaced the display (I had warranty)
After replacement, it started again. So a screen lasts 6 months, just great...
I've tried the magisk module posted in another thread, but it still happens (not every day, though).
Currently testing out the latest MIUI. Just a day in, nothing so far.
I didn't get this issue in a month of using MIUI 12.5.5, But immediately got it once after flashing ArrowOS 11.
Anyone else facing these ghost touches?
Edit: I installed Xiaomi.eu 12.5.5, let's see if I can reproduce the problem.
Finally reproduced with xiaomi.eu. Seems rare enough to live with though...
a day with xiaomi.eu, so far nothing.
arrowos unfortunately all the time

Categories

Resources