Related
Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN
The problem is coming from the magnetometer. I have the same issue, please check this thread: http://forum.xda-developers.com/showthread.php?t=1394264
The only workaround I found is to disable screen rotation and do a couple of restarts (not switch off). Of course, no compass in the end, but at least I can use the phone.
KaRsKiN said:
Hello,
I have an HTC Desire HD running Android 2.3.3. The device isn't rooted and I've never rooted it before.
I've checked on this site, and I've scoured Google all day but I haven't managed to find anything that matches my problem specifically, as explained below.
In the last couple of days I have been having a bizarre problem where after several minutes of normal use the phone becomes completely unresponsive or very laggy (to the point where it is unusable). This occurs whether I am using apps or simply looking at the home-screen.
The only thing that's responsive is the screen lock button, this works as normal. However when I then try to unlock the screen, the phone is still unresponsive and I'm unable to unlock it.
The only fix I've found (if you can call it a fix) is to leave the phone alone for a several minutes. If I do this I can once again unlock the screen as normal and continue using the phone, however after a few minutes of use it locks up again! This has been happening since last night now and I've found no way to break this cycle.
I did a hard reset to see if this solved the problem but it had no effect. The phone will boot as normal, and after a few minutes of normal use it will become unresponsive again.
I've also booted my phone without the SD card in just in case anything on this was causing the problem, still no improvement.
Has anyone else experienced a similar issue who could provide some insight as to what might be causing this issue? Any help you can provide would be greatly appreciated.
At first I thought this might have been a software issue, but as it persisted after the reset I'm beginning to think this might not be the case.
Thanks,
KaRsKiN
Click to expand...
Click to collapse
It is possible that your battery could be failing. See if att has one they will let you exchange.
If its not the battery then it could be a hardware issue. Just send it in for warranty if that is the case. You should still be covered as the phone is not yet a year old.
Sent from my Inspire 4G using xda premium
Gizmoe said:
It is possible that your battery could be failing. See if att has one they will let you exchange.
Click to expand...
Click to collapse
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.
Flussen said:
How should this be connected to the battery...?
Anyway, I think that it is a software issue rather than a hardware one. Maybe something is running in the background, using 100% of the cpu. You could try CPUNotify for realtime cpu monitoring.
If that doesn't work, you should try the magnetometer way. Maybe it's a new issue. Never heard about it though
I do what i want, because I can.
Click to expand...
Click to collapse
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium
Gizmoe said:
I'm not going to explain in detail about the relationship of voltages and CPU usage. The battery being bad can and has caused these exact issues. Just like if a power supply is failing it can cause a blue screen in windows. In android the phone rebooting itself or freezing is the equivalent to a blue screen. Since they have never rooted and are on a stock rom there is nothing except a hardware problem that would cause this. If the battery is not the culprit then one of the many components in the phone can cause freezes and reboots if it is failing. Android os does not allow a single task to take over the CPU. This is not a windows os. So like I said, just use your warranty and get it fixed. Stock phones should not be presenting this behavior, you would have to root it to cause these kind of problems.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Thanks for your help! My dad has the same device as me so I'll try swapping out the battery to see if this solves the problem. If not I'll try calling HTC to arrange a repair.
Any news? Was it the battery issue?
So most of us know about the System UI crash when using Chromecast, but this is even stranger. [Edit: an OTA update fixed this.] Some times, when I wake my phone up at the lockscreen or at times in the middle of a call - the touch screen stops responding. I can press and/or hold the volume buttons and there is a response on screen but I can not interact with the phone at that point. I can't continue to do battery pulls everytime. This is crazy. I'm on stock software. No crazy mods or anything. I've done a reset in the past and flashed the stock package again but this still happens every few hours. Only happens when the screen just wakes up...
Edit: This is a confirmed fix for me.
If you face the same issue, try:
open dialer
press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#
Hardware Device Test > Touch
update touch firmware
touch firmware version
wait 10 sec
reboot
I would say there is a misbehaving app causing the phone to lag in wake (that is all the unresponsiveness will be, extreme lag).
Sent from my Nexus 5 using Tapatalk
@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.
deedscreen said:
@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.
Click to expand...
Click to collapse
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Totally agree with @Epix4G on this one. I am assuming you had a korean variant? The SK Telecom stock image is pretty ugly. Took me 3 debloat attempts before I had it behaving the way I wanted it to, but before I debloated, I had some lag issues (SK Telecom... grrrhhh).
Historically, Korean carriers (much like AT&T and Verizon) love putting useless junk on the phones for "productivity" but really they are there to charge Korean users more for other services, etc.
If you haven't done so, I would root and debloat, and see how big of a difference it makes (absolutely amazing performance after debloating on my F400S).
^^^^ - Will take that into consideration.
This may be a possible fix for now, can't yet confirm
open dialer
press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#
Hardware Device Test > Touch
update touch firmware
touch firmware version
wait 10 sec
reboot
It may or may not help
EDIT: It's been a few weeks and I haven't had this issue again. Usually every 4-6 hours it used to happen after powering on the screen, but so far so good.
Tried that with 855 version, it's not working. This is REALLY depressing as i just got a new phone and from day one i'm having this problem. I just can't believe LG screwed up like this, and there's no mention of this anywhere online other than this XDA thread. I hope i don't have to root and install custom rom as this really defeats the purpose of the phone.
@deedscreen
I'm having exactly the same problem on an 850 and tried your firmware method. The version number of the firmware did not change after reboot.
ic_fw_version info
SYnaptics 5.5
PanelType 1
version: v1.22
IC_product_id[PLG313]
Touch IC : s3528(family_id = 1, fw_rev = 1)
What version is your firmware? Also, did you find out about the fix from somewhere?
I have the F400K, but just got a US T-Mobile edition, (I'll eventually switch my signature). I would honestly suggest waiting for an OTA update. Call LG so they can document this. If that touchscreen update method doesn't work, I'm not sure what to do. I found the method somewhere online, I don't recall where exactly. If someone can figure out how to side load the touch screen firmware from a working Korean model to others, that would be great. For now, keep calling LG. It won't do much at first, but at least they'll have reports of this issue.
I have (RAW) touch screen firmware version: 30 05 51 96
Same problem, but not only on lock screen
Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem, that the device is always unlocking itself, when in my front pocket. It's because of the Knock on feature. I deactivated this now.
But since yesterday i have the same issue: three times, i was unable to unlock my phone. The touchscreen simply did not respond. I had to remove battery. Today, I read this post and tried the firmware update of the touch, but I have the impression it did not change something in the version.
After this, today I had again once time the non responding touch while unlocking and shortly after, I had the issue after ending a phone call! The touch did no longer respond and had to remove the battery again!
I hope this is not a hardware issue, otherwise I will hurry up to the seller to exchange the phone, because its only 5 days old.
This is happening when the screen is on right? Or is the screen turning off and then not turning I again?
You need to keep Knock feature on, someone already said this. That's why your screen is freezing.
Daum Ex said:
You need to keep Knock feature on, someone already said this. That's why your screen is freezing.
Click to expand...
Click to collapse
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.
So bad: such a good phone and such an annoying bug
icon71 said:
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.
So bad: such a good phone and such an annoying bug
Click to expand...
Click to collapse
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...
That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...
Daum Ex said:
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...
That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...
Click to expand...
Click to collapse
Yes, indeed i also think about it. I got an official statement from support, regarding that the phone is unlocking all the time by itself in my pocket. They told me stuff like:
- this is a normal behaviour and can happen (!!)
- don't put your phone in the front pocket
- use the quick circle case to prevent...
- disable knock on (which is at least not possible over a standard setting, but only via the hidden menu).
I wrote back:
- that for me, this is not a normal behaviour
- that 90% of male users are wearing the phone in the front pocket
- that I don't like to buy a case only to prevent a bug of a premium telephone and
- finally, that they please could tell me, where and how to disable knock on
I am curious about their answer...
Good luck with that, disabling it through the settings doesn't change anything and they probably won't have a fix for months. They'll probably fix it though Android L update which will sadly come 6 months from official release at least.
Next time i purchase an Android phone i'm going with Nexus line...
icon71 said:
Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem...
Click to expand...
Click to collapse
So what happened? How is it doing now?
Hey everyone, I just wanted to report my results of this touchscreen bug.
Well, I've only had my D851 for a week now. Of course I rooted it the same day I received it.
I had no touch issues until after restoring apps with Titanium Backup. I'd restore all user apps, then very few system app via XML. Since I just upgraded from a Galaxy S3 T999 I limited the system apps greatly. So much in fact that I only restored 1 system app......Media Storage 4.4.4 (Playlist). THAT WAS MY SCREEN KILLER!
The media scan on my D851 would render my screen unresponsive. I could only hold the power button and click power off or restart or whatever else was on that power menu. Then the phone would reboot after minutes of of a dead screen.
I flashed back to stock and reproduced the same issue. So now I've been running this device for 3 days without any screen lockups. I just have to rebuild my playlist again LOL.
I hope this helps someone here.
Knock
If you turn off the ability to wake by knocking the screen, it causes this issue where the screen locks. Turn it back on and the problem seems to go away.
I think LG really has to deal with this issue.
Hi guys, I have red a lot about this issue but I'm still confused with my LG G3 855.
First I realize problem with unlocking the phone using double click. Tried to upgrade touch software firmware using hidden menu and the screen became almost totally unresponsive. Tried to re-flash original 5.0 and 4.4.2, factory reset, battery removed, etc. but no luck.
I'm wonder if this is a software problem or became hardware. Should I consider replacing display or problem is in motherboard?
I really don't know what to do! Appreciate any comments or suggestions!!!
Thanks in advance!
I've a SM-T700 Tab S 8.4 running lollipop, and I've recently noticed a bug. I don't know if it's new since the lollipop upgrade, but I didn't notice it before.
I often use it to read in the dark, so I turn the brightness down and set the touch keys to never light up. However, after a while the lights come on and stay on until the setting is altered again.
Anyone else getting a similar issue?
Hi! I think it's a common bug. I have the same problem and read that many people have it.
I'm not aware of any permanent solution, so for now i keep mine at 1.5 seconds (I'd prefer them off, but thats the best I could find!)
PS: Sorry for my English!
No need to apologize. Your English is perfect.
Sent from my SM-N900V using XDA Free mobile app
If the problem's widespread, what devices/ROMs has it been seen on? Is it Galaxy-specific, I wonder.
Same issue here
rosyatrandom said:
I've a SM-T700 Tab S 8.4 running lollipop, and I've recently noticed a bug. I don't know if it's new since the lollipop upgrade, but I didn't notice it before.
[....]
Anyone else getting a similar issue?
Click to expand...
Click to collapse
Same problem here, only on mine the only way I've found to turn them off once they come on is to restart the device. What a hassle.
I have the same problem, regardless of what I set the duration to. It never did this under Kitkat.
Mythra said:
Same problem here, only on mine the only way I've found to turn them off once they come on is to restart the device. What a hassle.
Click to expand...
Click to collapse
yeah same here, only fix I found was a reboot. think I flashed the Brazil version.
nismofreak said:
yeah same here, only fix I found was a reboot. think I flashed the Brazil version.
Click to expand...
Click to collapse
Hi! I have same problem with Brazil version also.
Might it be related to that version only?
pantezuma said:
Hi! I have same problem with Brazil version also.
Might it be related to that version only?
Click to expand...
Click to collapse
could possibly be... anyone with this issue not on the Brazil version?
Yes, same problem here with my new Samsung Tab S 8.4 SM-T700, stock 5.0.2
Putting it to 1.5 secs is the best I can do for now. I'm looking around on the app store to see if there's a different app to control this that might work (aside, the Galaxy S6 came with no way to turn these off and you have to use a separate app to do this).
nismofreak said:
could possibly be... anyone with this issue not on the Brazil version?
Click to expand...
Click to collapse
Mine is stock US (or whatever the official region is).
Mythra said:
Same problem here, only on mine the only way I've found to turn them off once they come on is to restart the device. What a hassle.
Click to expand...
Click to collapse
No need to restart/reboot, for me if I change the setting to something else (e.g., 1.5 secs etc) and then back to OFF it'll work for a while before it stays on permanently again.
levon9 said:
No need to restart/reboot, for me if I change the setting to something else (e.g., 1.5 secs etc) and then back to OFF it'll work for a while before it stays on permanently again.
Click to expand...
Click to collapse
I tried that with mine... won't work: no matter what I change the setting to they just stay on until I restart the device. I created a ticket with Samsung support last week, but no response from them so far.
Ah .. ok, that's interesting, thanks for sharing. Hopefully Samsung will issue a fix in the next update. Nice tablet otherwise.
I'm sure most, if not all, knew this, but it is definitely a software issue. I flashed CM 12.1 the other day and the touch keys stay off. Perhaps someone can look into the stock firmware and see if there's a way we can fix it ourselves?
Hey guys, I've had the same bug since upgrading to Lollipop and I found out it seems to be a bug with the power saving mode. If I turn it off, the bug stops happening. I'm also testing power saving mode with the "turn key lights off" option unchecked, and it seems to be working ok. This option can be found under settings, power saving, restrict performance.
I'll keep testing. If anyone tests it too please reply with your findings!
giancian said:
Hey guys, I've had the same bug since upgrading to Lollipop and I found out it seems to be a bug with the power saving mode. If I turn it off, the bug stops happening. I'm also testing power saving mode with the "turn key lights off" option unchecked, and it seems to be working ok. This option can be found under settings, power saving, restrict performance.
I'll keep testing. If anyone tests it too please reply with your findings!
Click to expand...
Click to collapse
I never use power saving mode, because I'm almost always near a charger, and I also had this issue. I don't think power saving mode has much to do with it. Not directly, at least.
Hi, I'm not using power savings mode, but have the same problem, so I'm not sure this mode is a factor (at least a sole factor).
Hi to all.
Somenone previously suggested this app:
https://play.google.com/store/apps/details?id=com.notquiteinsane.galaxybuttonlights&hl=en
I've been using it with and without power saving mode for 4 days and so far so good.
pantezuma said:
Hi to all.
Somenone previously suggested this app:
https://play.google.com/store/apps/details?id=com.notquiteinsane.galaxybuttonlights&hl=en
I've been using it with and without power saving mode for 4 days and so far so good.
Click to expand...
Click to collapse
Hi,
I suggested this app earlier upstream, however, it ended up not working for me. Not sure how it's working for you, but happy it is. (FWIW, I never use power savings)
Ok so I am having a strange touch screen issues with both mine and my wife's tab S 10.1. It started on mine several weeks ago. When using the device, the touch screen will all of a sudden stop responding. If I press the home button, the device goes to the home screen, it just does not respond to any touch. If I press the power button to put the device to sleep and push it again to turn it back on the screen is working again but it will freeze up again, sometimes in less than a minute. When it first happened I tried to do a factory reset to see if that would help and the problem actually occurred during the initial device setup then so I know it's not related to an App that I have installed. I have sent mine to Samsung now three times trying to get them to fix it. They have replaced the screen once and said that there is nothing wrong the second time (still waiting on the determination of the third time). I have tried to research the issue but have not seen anyone experiencing the same thing. I do not have the rebooting issues that others have mentioned and turning the screen off and then back on does make it work, at least temporarily. I only remember noticing it since upgrading to Android 5 so I am going to try getting the device downgraded to Android 4.4.4 to see if that helps. Wanted to see if anyone had any other ideas. Samsung has basically told me if their techs say there isn't a problem they won't do anything for me.
A few people have mentioned touchscreen problems after upgrading to v5.0.2 mostly 8.4" but some 10.5" have you had any horizontal/vertical lines on the screen.
John.
Tinderbox (UK) said:
A few people have mentioned touchscreen problems after upgrading to v5.0.2 mostly 8.4" but some 10.5" have you had any horizontal/vertical lines on the screen.
John.
Click to expand...
Click to collapse
I have never noticed any lines. I have noticed after the first time at the repair center that the touch screen also seemed to be acting erratically, jumping around when trying to scroll or pan instead of having smooth motion. If I am able to get the device downgraded to KitKat and that improves things, I will just stay there until they figure out what is wrong with Lollipop.
I have stayed on kitkat because of the problems with lollipop, it`s just not worth it to me, but the majority of people don't seem to have any problems with it, I cannot see how upgrading to lollipop affects some touchscreens and not them all, but some people have reported the problem after upgrading i just don't know what to say.
It is normal for the touchscreen to behave erratic if you use it while your tablets is being charged, it is mentioned in the user manual.
I would say you have a faulty touchscreen, do you use a screen protector, have you tried the setting that increases the sensitivity of the touchscreen.
John.
I did not know about the charging item so that might explain the erratic behavior. I thought it might explain the screen locking up too but I know that has happened at times when I am not charging the device. I will be interested to see what happens this time when it comes back the third time from Samsung and whether downgrading my wife's device helps the issue on hers or whether we will need to fight with Samsung about hers as well.
For a couple months, I've had exactly the same problem on my Galaxy Tab S 10.5 (SM-T807V). It comes and goes in severity; some days, I lose all touch input every 5 minutes, it seems, while other days, I can go hours without trouble. Using the device without a case seems to help, as does restarting it, at least temporarily.
I have not sent my device to Samsung, nor have I performed a factory reset. But based on your experience, I'm not sure if either option is worth it.
Hi.
I would suggest removing any screen protector and cleaning the screen looking for any damage, download a touchscreen tester app from google play and testing your screen.
After searching around i found an touchscreen recalibration app for android, but i am very wary of it being fake or causing more damage or that it is for a specific brand of phone/tablet.
EDIT: I used an hex editor, and found this text within the apk file, see photo below.
John.
Well Samsung is finally sending the device back to me. This time they said the found the problem and replaced the main board and updated the software. So we will see what happens when it gets back to me tomorrow.
For anyone who is having this problem like I did. My wife has not had problems since she stopped using the device while it was charging. I have not had problems with mine since it got back related to this but whether that was Samsung fixing the issue or the fact that I also am not using it on my charger, I do not know. So if anyone else if having the problem, try the charger thing; otherwise, you may be looking at some kind of hardware issue that Samsung will have to resolve for you.
Most devices behave erratically while being charged. My HTC does it so does my tab.
Samsung even mention it.
Hi, i am having EXACTLY the same issue. The tab toucj freezes and normalizes if i lock it and unlock it with home button. I think its a software issue.
Sent from my GT-N7000 using Tapatalk
I have two of these from Verizon (T807V) and after updating them to 5.0.2 they both have this same behavior.
Quite annoying.
Any luck finding a cure ? I have noticed that the ram usage gets crazy. Any given time 1.8 gb is utilized out of he 2.77 gb available. I have uninstalled quite a few apps and shut down background processes but still the system is eating too much ram. Can any one help me on how to monitor aap ram usage ?
Sent from my SM-T807V using Tapatalk
Hi.
I was reading the HTC forum as i have qone of their phones, and i read that some people were using an Samsung touchscreen app to boost the touchscreen as they were having problems, the app is called "SGS Touchscreen Booster" link below, The Tab S1 has it`s own touch screen booster in the settings, maybe try that first.
https://play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com&hl=en_GB
http://forum.xda-developers.com/showthread.php?t=1581098
John
siddiqui.nauman said:
Any luck finding a cure ? I have noticed that the ram usage gets crazy. Any given time 1.8 gb is utilized out of he 2.77 gb available. I have uninstalled quite a few apps and shut down background processes but still the system is eating too much ram. Can any one help me on how to monitor aap ram usage ?
Sent from my SM-T807V using Tapatalk
Click to expand...
Click to collapse
That's how android works. Its pointless trying to reduce ram usage if there is still ram to spare.
Android utilises ram not wastes it.
siddiqui.nauman said:
Any luck finding a cure ? I have noticed that the ram usage gets crazy. Any given time 1.8 gb is utilized out of he 2.77 gb available. I have uninstalled quite a few apps and shut down background processes but still the system is eating too much ram. Can any one help me on how to monitor aap ram usage ?
Sent from my SM-T807V using Tapatalk
Click to expand...
Click to collapse
I had multiple problems with 5.0.2, ram hogging, touchscreen problems, my solution was to root and install a custom rom 4.4.4 the tablet is so much more responsive after reverting back to kitkat. I know it's not a solution for everyone but it fixed mine (SM-T800). Just throwing it out as an option.
Used kies today to upgrade to the latest firmware but still the problem continues. I have the Samsung sm t807v Verizon locked. Is there a way I can downgrade it to kit kat? Xda experts are saying it's bootloader is locked
Sent from my SM-T807V using Tapatalk
Steve1698 said:
I had multiple problems with 5.0.2, ram hogging, touchscreen problems, my solution was to root and install a custom rom 4.4.4 the tablet is so much more responsive after reverting back to kitkat. I know it's not a solution for everyone but it fixed mine (SM-T800). Just throwing it out as an option.
Click to expand...
Click to collapse
This is a strange one I used to have the opposite. 4.4.4 every now and then touch screen stopped responding. Pressing power resolved it.
When I upgraded to LL the problem went away.
However I mostly use custom builds. At the moment the best for me is PhoeniX ROM.
Absolutely bug free so far.
Can't say I had any issues with Ironrom either.
ashyx said:
This is a strange one I used to have the opposite. 4.4.4 every now and then touch screen stopped responding. Pressing power resolved it.
When I upgraded to LL the problem went away.
However I mostly use custom builds. At the moment the best for me is PhoeniX ROM.
Absolutely bug free so far.
Click to expand...
Click to collapse
I'm running BlissStalk (discontinued) but I haven't had any issues with it. I was running the CM11 unofficial also without issues. But the stock 5.0.2 it had on it when I purchased it (used) had issues. All my devices eventually end up with a custom rom eventually!
---------- Post added at 02:19 PM ---------- Previous post was at 02:15 PM ----------
siddiqui.nauman said:
Used kies today to upgrade to the latest firmware but still the problem continues. I have the Samsung sm t807v Verizon locked. Is there a way I can downgrade it to kit kat? Xda experts are saying it's bootloader is locked
Sent from my SM-T807V using Tapatalk
Click to expand...
Click to collapse
I flashed stock kitkat firmware via Odin... But it is a different tablet than yours (SM-T800). I found the following thread when I was trying to do it. Just make sure you flash the firmware for your specific model.
http://forum.xda-developers.com/galaxy-tab-s/help/sm-t800-best-to-downgrade-5-0-2-to-t3069929
Bootloader unlocking
So basically searching around the internet to find a kitkat firmware for this. I think it can be downgraded but I need the stock firmware for the sm-t807v.
XDA forums have support for the other variants but for the one I have which is Verizons sm-t807v there are no STOCK firmwares anywhere.
Ashyx and steve if you know any resource, please help me out. I need to get this fixed. I don't have access to any verizon stores where I could go and get this fixed or sorted. It just me and the internet.
After the upgrade to Lollipop the 3 seconds light on the buttons stopped working. I can force the buttons to always lit or to be turned off but the 3 seconds option won't take. Any one experienced something like this with Lollipop?
I've tried doing a complete reset and than a restore to factory settings. No change.
The thread below might help.
http://forum.xda-developers.com/galaxy-tab-s/help/touch-key-duration-bug-lights-stay-set-t3128015
John.
Never experienced this in any of the Roms I've installed stock or custom.
If this is/was a bug I would have thought Samsung would have brought out an update to fix it by now.
Tinderbox (UK) said:
The thread below might help.
http://forum.xda-developers.com/galaxy-tab-s/help/touch-key-duration-bug-lights-stay-set-t3128015
John.
Click to expand...
Click to collapse
Thanks. Tried the app from that thread but I'm getting the same behavior. Always on works. always off works ,1.5 seconds stays always off.
ashyx said:
Never experienced this in any of the Roms I've installed stock or custom.
If this is/was a bug I would have thought Samsung would have brought out an update to fix it by now.
Click to expand...
Click to collapse
Well, there's definitely a bug on my device and on the devices of users from the other thread. I suspect that only some region roms are effected with this bug. I've read that guys from Brazil are experiencing this. My rom is an Israel \ Hebrew one so this might be related.
Shasoosh said:
Thanks. Tried the app from that thread but I'm getting the same behavior. Always on works. always off works ,1.5 seconds stays always off.
Well, there's definitely a bug on my device and on the devices of users from the other thread. I suspect that only some region roms are effected with this bug. I've read that guys from Brazil are experiencing this. My rom is an Israel \ Hebrew one so this might be related.
Click to expand...
Click to collapse
Well considering the fact I've run a French, Swiss, Nordic, UK, Arab emirates and Canadian rom on my tab without issue, I doubt it's rom related.
Its more likely to be a kernel issue if it is actually software related.
Update your kernel and you may find the problem goes away.