There are so many recoveries available and I tried them all.. most dont even get flashed. Anyway, I ended up with the only one that seems to work for my N5120, CivZ_rev1.1-PhilZ_5. I succesfully flashed an 4.2.2 though the benchmarks are a disaster, the battery vanishes in 2 hours and the performance is a joke.. Quandrant gets me less than 2000...
That leads me to try and flash a 4.4.2.. but every single one the flash fails and gets aborted with a STATUS 7 message.. no matter the build, kind, or if it comes from the internal SD card or the External SD.. always fails. What the hell am I doing wrong and how can I flash this Tab?... I feel so frustrated.. nothing like this ever happened to me.
Thanks much for the advice..
Don't know if that helps but I had similar issues. Ended up flashing official CM11 Nightlies, the best I could find for N5120 up to now. No Pen support but the rest is working ok. Quadrant gives me a score of 5095.
For flashing the only recovery that worked for me (and I also tried many giving Status 7) was / is PhilZ Touch 6 based on Clockworkmod v6.0.4.7.
There might be more recent now but as this one worked, I sticked with it.
Envoyé de mon SM-N9005 en utilisant Tapatalk
LuMe96 said:
Don't know if that helps but I had similar issues. Ended up flashing official CM11 Nightlies, the best I could find for N5120 up to now. No Pen support but the rest is working ok. Quadrant gives me a score of 5095.
For flashing the only recovery that worked for me (and I also tried many giving Status 7) was / is PhilZ Touch 6 based on Clockworkmod v6.0.4.7.
There might be more recent now but as this one worked, I sticked with it.
Click to expand...
Click to collapse
Thanks for your advice.. PhilZ Touch v6.0.4.7 finally worked.. is crazy there are so many recoveries for the Note 8 and almost all have problems or are not compatible with KK..
I flashed the latest CM11 but I have LOTS of problems.. when the Tab is power off and charging, I get is a frozen image of the battery loading with full screen brightness but no charging animation or charging level information and basically the Tab doesn't charge and just heats up, I have issues with the menu key (left to the home button hardware softkey), I have problems with the home button that insists usually activating a double click when I only press it once, I have very long delays in locking wifi and GSM signal and several other small things that bother me.. and I come from rooted stock 4.2.2 with a costume Kernel that I could overclock the Tab to 1.9GHz.. but no Kernels available seems for 4.4.2.. the performance I get with CM11 is horrible compared to what I had with stock 4.2.2 and the battery lasts NOTHING..for me CM11 is unusable at this point and the developer doesn't bother to reply to any questions..maybe some problems are specifically with my unit and the CM11 ROM and maybe some problems because of the modem I have (my N5120 is from Hong Kong).. there are lots of other modems available but I have no idea what to try and worry make things worse..
I am curious about your experience with the other KK ROMs.. I want try to PAC, Paranoid and SlimKat..you dont like them? What problems you had with them?
Thanks again for your input
Hi,
I do agree regarding the charging "Device off" issue, but I tend to never switch my device off, so I can live with that. For the rest I do not recognize any of the issues you listed. 3G / 4G working fine, WiFi also and no problems with the hardware buttons.
By the way, mine is also HK version. I bought during my last trip to HK last year.
I tried PAC Rom, and had no major issues either, except missing Recent Apps manager. Didn't try any other ROMs up to now. I tend to prefer "basic" ROMs and add some needed stuff through Xposed. This is also the reason I decided to switch to CM11 when it became official. Haven't found the need to come back to PAC Rom since. It's not TOP but does the job for me. As you are speaking about battery, I do easily get 4 hours of Plex Video Playback over WiFi at decent screen brightness / 4 to 5 hours video Playback with MX Player and video stored on external SD-Card. Will however probably revert to TW ROM as soon as a 4.4.2 version is released to recover PEN functionality.
Did you use the official CM11 from their website? I know that there are older non official versions around (which I initially tried but had problems with).
I attached a screenshot of my about screen so you can have a look at baseband and kernel.
LuMe96 said:
Hi,
I do agree regarding the charging "Device off" issue, but I tend to never switch my device off, so I can live with that. For the rest I do not recognize any of the issues you listed. 3G / 4G working fine, WiFi also and no problems with the hardware buttons.
By the way, mine is also HK version. I bought during my last trip to HK last year.
I tried PAC Rom, and had no major issues either, except missing Recent Apps manager. Didn't try any other ROMs up to now. I tend to prefer "basic" ROMs and add some needed stuff through Xposed. This is also the reason I decided to switch to CM11 when it became official. Haven't found the need to come back to PAC Rom since. It's not TOP but does the job for me. As you are speaking about battery, I do easily get 4 hours of Plex Video Playback over WiFi at decent screen brightness / 4 to 5 hours video Playback with MX Player and video stored on external SD-Card. Will however probably revert to TW ROM as soon as a 4.4.2 version is released to recover PEN functionality.
Did you use the official CM11 from their website? I know that there are older non official versions around (which I initially tried but had problems with).
I attached a screenshot of my about screen so you can have a look at baseband and kernel.
Click to expand...
Click to collapse
Yes I downloaded from their official link (I think):
http://download.cyanogenmod.org/?device=n5120
Im running cm-11-20140525-NIGHTLY-n5120.zip
Ok, strange I'm running the exact same version.
Regarding WiFi and network issues you might want to check modem / baseband version (and kernel). Other than that I don't see why there is such a difference in behavior between your device and mine, sorry.
Envoyé de mon SM-N9005 en utilisant Tapatalk
Related
So I've been having a bit of trouble with my t989 lately, when I try unlocking the phone I will either get a black screen (the lock screen will appear for a split second before going blank if I hit the lock button again) or it won't track my finger movements on the screen. If I manage to unlock the device I end up seeing numerous graphic glitches ranging from the bar at the top w/ the clock/battery meter just gone and the keyboard not working.
I'm runing CM9.0.0 because I had issues with 10.2 (battery wouldn't charge) and 10.1.3 (similar to my lock screen issues but not as severe, still agitating) and also 9.1 which had the same exact issues as I'm having now. I've tried installing with different gapps but the same thing happens. The phone will work for a day or two, then the glitches come. After resetting, everything is normal for a day or so, then it's normal a few hours, etc. The time is getting narrower between reboots and it's a bit frustrating.
Does anyone know what I could be doing wrong, if anything? I flash via twrp and wipe, then install the rom, then install gapps, then reboot, wait 20min, reboot, and go about my business w/ the setup and such. I would be fine going back to 10.1.3 but jellybean roms and snapchat don't really like to work together on this phone for some reason. It's really the only app I use because it seems like the only way my friends want to communicate nowadays, so I'd prefer to stay on ics if possible...
If anyone can give any insight I'd really appreciate it
greenghoul said:
If anyone can give any insight I'd really appreciate it
Click to expand...
Click to collapse
Have you tried using Odin to flash back to stock? That is usually the recommended step if you are having problems with custom ROMs.
And the newest stock is 4.1.2, so at least you wouldn't have to be on ICS.
meekrawb said:
Have you tried using Odin to flash back to stock? That is usually the recommended step if you are having problems with custom ROMs.
And the newest stock is 4.1.2, so at least you wouldn't have to be on ICS.
Click to expand...
Click to collapse
I'll give that a try. Odin is just the program used to root originally, correct? Also, I want to stay on ICS if possible. So after doing that I'm going to try CM9 again and see how that works.
Anyway, the past few days I've been using AOKP mr2 milestone 1 and it's been okay. For some reason the battery life is bad even with juice defender and a task killer taking care of things. In a matter of minutes after clearing tasks I'm down from ~350mb of ram free to 60. Is that normal with that rom?
I'm not sure what to do at this point. I'm not the best with technology but i figured i was smart enough to figure this out...
bump.
I still haven't tried flashing w/ odin yet. Does anyone know where I can find a gingerbread stock rom? I've been looking for a while and can only find the jellybean one. Since I want to stay on ICS what I want to do is go from gingerbread and up to that rather than downgrading from the jellybean stock rom if that makes sense.
Few days earlier I started to notice this problem after 5 months of use of my device. My screen starts rapidly shaking left to right and front touch panel stop working, it happen when I freshly open an apps. To temporarily fixed it, I have to press power button to turn off the screen. Is it a hardware or software problem?
Did you flashed any rom or kernel?
Do you use trickster?
Some people sayed that uninstalling trickster solved their ghost touches on the keyboard (may not work in your case).
I had a similar problem and was because of a kernel.
If you had modified anything try to use stock for a while and see if the problem persist
Enviado do meu Optimus G através de Tapatalk
Stock, I guess I should wait for official kitkat. Dont have time thinkering my fone atm.
I was ghosts touches on my screen. One was pressed on all sides. To fix it I had to turn off and turn on the screen. I decided to change the touchscreen and the problem was fixed. Now it works ok.
Sorry my english.
Enviado desde mi LG-E975 mediante Tapatalk
where do you get you're replacement touchscreen? any online site that offer spare parts?
yawako said:
where do you get you're replacement touchscreen? any online site that offer spare parts?
Click to expand...
Click to collapse
I bought it on ebay. Screen+touch+ frame. This option:
http://pages.ebay.com/link/?nav=item.view&id=111278902215
But You can buy other options.
1. Touch + screen+ frame (medium dificult)
2. Touch + screen without frame (best option)
3. Only touch screen. (very dificult option)
Many people have told me that the best option is 2, without frame to not be taking off parts that are originally attached to the frame.
You can see totorials on youtube
Ghost Touch now keeps rapidly pulsing at the buttom edge of my screen (portrait) my phone is sometimes uncontrollable. I never thought this kind of newer high end device gets broken so easily under short period of time. I never experienced this from my good old Galaxy Y, Xperia mini and X8 that I accidentally deep under water even now still working in mint condition. So sad with LG products. I was planning to buy LG G Pad but because of this I probably get Nexus 7 instead.
Im going to sell this for $155
Reflash it again with stock firmware twice, problem still persist
Its now a hardware issue
Touch screen seems deteriorating overtime. At first Ghost Touch, then on the next day a dead touch portion just above the home screen panel where the ghost touch first occurred rapidly moving back and then after few days a ghost touch appeared again just below in the middle of the screen (portrait) then after an hour probably about 1.5mm size thickness dead touch. Now a I have 2 horizontal dead touch portion of my screen and probably more to come if I keep using it.
Few days ago i'v got first phaton/ghost touch problem. I used Omni 4.4.4 so
- reflash to clean OmniRom (try few kernels) - the same
- flash to Android L Preview - the same
.....
fu***
Install - ARTMod ROM so 99,9%of stock - and as for now all its ok.
Strange.
Update:
One day and zero problems.
htomasz said:
Few days ago i'v got first phaton/ghost touch problem. I used Omni 4.4.4 so
- reflash to clean OmniRom (try few kernels) - the same
- flash to Android L Preview - the same
.....
fu***
Install - ARTMod ROM so 99,9%of stock - and as for now all its ok.
Strange.
Update:
One day and zero problems.
Click to expand...
Click to collapse
Please, can you post the link from the exact same rom?
I've got so many ghost touches on an exact same point my screen (I posted that on another thread on this board) that made me got another phone, typing was impossible (the touches were on the left-down corner, right on swiftkey settings -_- )...I've tried many many roms, but nothing worked yet...
Thank you a lot!
dashcsn said:
Please, can you post the link from the exact same rom?
I've got so many ghost touches on an exact same point my screen (I posted that on another thread on this board) that made me got another phone, typing was impossible (the touches were on the left-down corner, right on swiftkey settings -_- )...I've tried many many roms, but nothing worked yet...
Thank you a lot!
Click to expand...
Click to collapse
On this ROM 0 phantom/ghost touch
http://forum.xda-developers.com/optimus-g-intl/development/rom-e97520a-eu-4-4-2-artmodv3-0-te-10-t2811342
OK, this is freakin' weird...
I have been running KitKat on my F180S pretty much from the time it got released (different versions: full stock, VDT, Sling...). Yesterday, out of the blue, my digitizer started getting crazy with ghost touches in the upper portion of the screen (around the strip where Q-slide apps usually are in the notification shade, or the clock area on a weather widget where most people have it). This made the phone 100% unusable, as it was constantly registering touches. Rebooted to recovery to do a factory reset, and the problem was persistent in the recovery, too (I am using PhilZ Touch). So, at that point it looked like a hardware issue to me. To clear my consciousness, I opened the phone, disconnected the digitizer, cleaned the connectors, plugged it in again. No dice. Still, I thought about reflashing a full stock KDZ, just for the heck of it (no root, no custom recovery, locked BL). Here is what happened:
1. F180S V30c KitKat - same problem.
2. F180S V30b KitKat (downgraded a notch) - same problem.
3. F180S V20n Jelly Bean - everything is working fine, no ghost touches. Huh?!?
4. Rooted V20n, unlocked BL (Mako method) and flashed CWM using FreeGee - no problem, everything is still OK.
5. Flashed my favourite JB ROM - no problem, everything is still OK.
So, the phone is now running on rooted JB, with unlocked BL and CWM recovery, with no touchscreen problems whatsoever. I may try going to KK again at some point, but will just leave it for now, as I need a stable working phone.
WTF??? I am just scratching my head, trying to understand where the issue came from. It appears to be directly related to KitKat, since eliminating unlocked BL and custom recovery didn't solve the issue, but going back to JB (either full stock, or unlocked BL with CWM) totally cured it. The most bizarre thing is that it started out of nowhere, as I didn't do anything to my phone recently, apart from installing some apps here and there...
kt-Froggy said:
OK, this is freakin' weird...
I have been running KitKat on my F180S pretty much from the time it got released (different versions: full stock, VDT, Sling...). Yesterday, out of the blue, my digitizer started getting crazy with ghost touches in the upper portion of the screen (around the strip where Q-slide apps usually are in the notification shade, or the clock area on a weather widget where most people have it). This made the phone 100% unusable, as it was constantly registering touches. Rebooted to recovery to do a factory reset, and the problem was persistent in the recovery, too (I am using PhilZ Touch). So, at that point it looked like a hardware issue to me. To clear my consciousness, I opened the phone, disconnected the digitizer, cleaned the connectors, plugged it in again. No dice. Still, I thought about reflashing a full stock KDZ, just for the heck of it (no root, no custom recovery, locked BL). Here is what happened:
1. F180S V30c KitKat - same problem.
2. F180S V30b KitKat (downgraded a notch) - same problem.
3. F180S V20n Jelly Bean - everything is working fine, no ghost touches. Huh?!?
4. Rooted V20n, unlocked BL (Mako method) and flashed CWM using FreeGee - no problem, everything is still OK.
5. Flashed my favourite JB ROM - no problem, everything is still OK.
So, the phone is now running on rooted JB, with unlocked BL and CWM recovery, with no touchscreen problems whatsoever. I may try going to KK again at some point, but will just leave it for now, as I need a stable working phone.
WTF??? I am just scratching my head, trying to understand where the issue came from. It appears to be directly related to KitKat, since eliminating unlocked BL and custom recovery didn't solve the issue, but going back to JB (either full stock, or unlocked BL with CWM) totally cured it. The most bizarre thing is that it started out of nowhere, as I didn't do anything to my phone recently, apart from installing some apps here and there...
Click to expand...
Click to collapse
Kinda like my situation.
I have the sprint version of the phone,in every kitkat GEE ROM I have ghost touches, but not in Gproj kitkat ROMs neither in stock or JB.
some weird sh*t is happening here lol
FcoEnrique said:
Kinda like my situation.
I have the sprint version of the phone,in every kitkat GEE ROM I have ghost touches, but not in Gproj kitkat ROMs neither in stock or JB.
some weird sh*t is happening here lol
Click to expand...
Click to collapse
Yeah... But at least in your case the problem seems to be consistent. I was using my phone without any issues, and then it just crapped out for no apparent reason. Nothing changed, same ROM that was working fine before...
kt-Froggy said:
Yeah... But at least in your case the problem seems to be consistent. I was using my phone without any issues, and then it just crapped out for no apparent reason. Nothing changed, same ROM that was working fine before...
Click to expand...
Click to collapse
It started the same way for me.
....
The same thing happened to me. Are you guys familiar with Sky Vega phones? I had a Vega Iron before and also it began having ghost touch issues after upgrading to kitkat. I was frustrated, i also flashed any custom rom i could search and no luck at all. I just sold it recently! and i heard this ghost touch issue is also a common on Nexus 4.
dashcsn said:
Please, can you post the link from the exact same rom?
I've got so many ghost touches on an exact same point my screen (I posted that on another thread on this board) that made me got another phone, typing was impossible (the touches were on the left-down corner, right on swiftkey settings -_- )...I've tried many many roms, but nothing worked yet...
Thank you a lot!
Click to expand...
Click to collapse
http://forum.xda-developers.com/optimus-g-intl/development/rom-e97520a-eu-4-4-2-artmodv3-0-te-10-t2811342
Hello everybody,
I have the same problem with my LG - ghost touch and dead zones on the display. First installed the ROM from this link - http://forum.xda-developers.com/opti...te-10-t2811342 , but the issue still exist.
Then change the display with a new one. Dead zones vanished but ghost touch doesn't. Tried some other ROMs even the original stock ROM.
When I installed the new display the ghost touch is mostly when I use Facebook Messenger.
What can I do in this situation?
I've been getting these glitches/artifacts/tearing on any 4.4+ rom on my T-mobile S3.
It's like the status bar will glitch down to the bottom of the screen.
I'm currently on a 4.3 stock rom (ENC2), It's been rooted with the samsung toolkit and has knox disabled (at least according to the app).
I've tried most current d2lte roms, PA, spirit, ACIP...ect.) and they all have it.
I know for a fact I'm missing something. I just can't remember what it is for the life of me. I know it has something to do with the bootloader/binary. I seem to remember when 4.4.1 came out there was something with the bootloader we had to do and no matter what I search nothing is coming up with the correct solution.
I'm hoping someone could tell me what i'm missing because it seems painfully obvious and I'm missing it, . I really don't enjoy using TW.
We don't ever mess with the bootloader or other parts of the base firmware, so maybe you're thinking of a different device?
When did it start? What was the last thing you did (flash)? Tbh, to me it sounds like a hardware problem. Maybe a connector got loosened, or some moisture/water damage, or even heat damage could cause what you are describing. Especially if its happening on every ROM.
Flash the stock NC2 firmware via Odin and factory reset. If it still happens after that its almost certainly hardware related.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Does it also happen with touchwiz?
So. I ran the knox removal thing from the samsung toolkit and now I don't see them on the latest CM nightly.
I have to test a few other roms but I don't know, it's somehow fixed, thank you for the responses.
Glad to hear it. Be careful with the toolkit though. It is not supported and has bricked devices.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
After giving it a few days the issue came back.
I've tested this on a stock nc2 touchwiz as well as your (doc) latest likewise release with no issues with the screen or anything.
For the non touchwiz I tried aicp latest 4.4.4, the latest cm11, the latest aospa weekly and a 4.3 AOKP release (milestone2).
The glitch issue wasnt in the cm release for a day or so then showed up, all others showed up instantly.
I also emergency recovered via kies. Then rerooted. I'm also using the latest twrp
Here is a logcat of the ROM I'm currently on, the 4.3 AOKP. I wish I had more of an understanding of logcats so i knew if I posted the right section.
http://pastebin.com/UyZFHriB
I was curious so I booted up a nandroid of aicp and then restored a backup of the boot from likewise. Results were minimal glitching but no connectivity at all. APNs didn't load and WiFi is broken. I'll post a video shortly of the screen.
The only thing that jumps out on that logcat is where you have this kind repeated several times in a row:
09-18 13:35:38.752 W/ActivityManager( *761): Permission denied: checkComponentPermission() owningUid=10060
But I honestly don't know what its referring to. But I will say that since it appears to be happening on every rom, even stock, it sounds more like a hardware issue. Display problems usually are to begin with, but almost any problem that persists across multiple ROMs and wipes can usually be blamed on a hardware malfunction.
Watch a disassembly video on youtube, then open it up and reseat all connectors. (Don't mess with the antenna. Its fragile and not related to the issue at hand.)
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
But I will say that since it appears to be happening on every rom, even stock, it sounds more like a hardware issue.
Click to expand...
Click to collapse
That's the odd thing, On both 4.3 and 4.4.2 versions of touchwiz I don't get the glitching. Only on AOSP based roms. I could just go stick with a touchwiz based rom and be done with it but my personal preference is not using touchwiz. I'm just confused as to what is actually causing this.
I'm guessing it has to have something to do with the bootloader and baseband.
I think i did forget to mention this is a "refurbished" warranty replacement, i regret that I don't recall which specific version it had as stock, I'd guess it has to be enc2?
Here is a poor quality video to show whats happening, on the home screen you see the glitching where the status bar glitches down to the bottom. I tried to get it to do what it sometimes does in both the MLB app as well as the reddit app but it decided not to be as noticeable this time.
http://youtu.be/ZsZL1Okio-A (sorry about the added music )
Just a side question, I couldn't seem to find a definitive answer, but was it ok to downgrade within the 4.3 bootloaders? I thought I remember reading that as long as you don't go from 4.3 to 4.1.2 it was fine.
Soryy I misunderstood before about it happening on stock. Have you tried any different kernels? I'd suspect that before bootloader. But since it's a refurb, there's just no telling for sure.
Once on 4.3 you cannot downgrade your firmware at all. You can flash older roms, but that's it.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Well ATM its working.. But lately the lag on my device makes it stutter so bad it freezes up then slowly comes back. Then sometimes the screen goes black and my device won't do anything.. The screen doesn't come back on. I have to hold the power button and sometimes volume buttons together to get it to restart to be usable.
I have only experienced this on 5.0.x roms 4.4.4 never did this
Ideas? Suggestions? Thanks
Sent from my Nexus 7 using XDA Free mobile app
I've never had those issues on any lollipop ROMs (at least not for this device).
Personally I'm not a big fan of CM, have you tried any other ROMs and/or kernels? Have you flashed a custom kernel or adjusted any kernel settings that could be causing this? Are you using any mods (like Xposed)?
I'd suggest trying out some other ROMs (possibly even just rooted stock) and starting out with a clean flash, with no mods/kernel changes initially, and see if you still have the issue.
PrizmaticSmoke said:
I've never had those issues on any lollipop ROMs (at least not for this device).
Personally I'm not a big fan of CM, have you tried any other ROMs and/or kernels? Have you flashed a custom kernel or adjusted any kernel settings that could be causing this? Are you using any mods (like Xposed)?
I'd suggest trying out some other ROMs (possibly even just rooted stock) and starting out with a clean flash, with no mods/kernel changes initially, and see if you still have the issue.
Click to expand...
Click to collapse
I'll give that a try.. I haven't done anything to it because upgraded the bootloader to like 4.04 and installed CM12 on it. It ran so good till like a week or so ago and now its just trash. A case with a magnet for sleep mode wouldn't have anything to do with this would it? But first things first, I'll try a simple 5.0.2 rom and see what happens.
Thanks
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.