So I bought a used N4 sold as is because the seller said he had some issues with the ROM and the touch sensitivity and all it needed was a stock ROM flash. I took up the challenge and flashed stock 4.4.4.
While I'm at the home screen everything's fine, as soon as opened the app drawer there were random touches all over the bottom half of the screen. Some were shown in the center and many at the bottom left corner but most were just random. I mean like 7-8 touches per second. The same happened whenever I went into play store, Opera or Chrome. Didn't test it further since I decided to try another rom.
Flashed Purity ROM and at first glance it worked flawlessly. Not random touches in home screen, app drawer or settings. Then I flash Gapps and the same thing happens with Play and Opera.
The funny thing is that the problem persists but at different circumstances. Can't pinpoint the exact cause. Should I get a new screen and try? Or maybe something else is at fault there?
I've been having the exact same problem as you. It started after I replaced the screen and the usb flex.
Ghost touches 1-2 each second only on some apps (none on homescreen or settings). I noticed that it happen in 4.4.4 app drawer but not in the 4.2.2 app drawer. I got almost no ghost touches on 4.2.2 messaging app also. It happens in almost any app, like play store, dropbox,chrome....
I thought it was the battery so I replaced it, but it did not fix it.
I have been trying to troubleshoot the problem but I ran out of theories. I wish the best luck to find the solution, as I almost gave up on it. If you happen to solve it tell me.
I think i found out what's causing this issue.
My theory was that apps with a lot of white would trigger the ghost touches. So I tested with flashlight screen apps that only show white on the screen. As expected the ghost touches only started to appear when i turned the flashlight on.
Therefore my theory was correct.
In my case I will contact the seller that sold me the screen to see if I can get a replacement.
I've had the intermittent touch screen issue, just above the capacitive buttons and also the ghost touches.
Started about 2+ weeks ago.
I reverted back to the stock "HOME" launcher instead of the Google Now launcher and that seemed to have fixed the issue.
I will have to keep an eye out to see if it lasts.
Nexus4 Ghost touch navbar fixed (for rooted only)
Nubrig said:
So I bought a used N4 sold as is because the seller said he had some issues with the ROM and the touch sensitivity and all it needed was a stock ROM flash. I took up the challenge and flashed stock 4.4.4.
While I'm at the home screen everything's fine, as soon as opened the app drawer there were random touches all over the bottom half of the screen. Some were shown in the center and many at the bottom left corner but most were just random. I mean like 7-8 touches per second. The same happened whenever I went into play store, Opera or Chrome. Didn't test it further since I decided to try another rom.
Flashed Purity ROM and at first glance it worked flawlessly. Not random touches in home screen, app drawer or settings. Then I flash Gapps and the same thing happens with Play and Opera.
The funny thing is that the problem persists but at different circumstances. Can't pinpoint the exact cause. Should I get a new screen and try? Or maybe something else is at fault there?
Click to expand...
Click to collapse
Hi everyone. this is my first post. i may make some grammar mistakes, because english is not my native language.
I found a solution for the ghost touch issue on my nexus 4, so maybe it can help who is having the same problem.
1- Download and instal the NOMone Resolution Changer on Play store
(this is my first post here, so i cant paste de link here, but you will not have trouble to find it)
2- when asked, Allow superuser
3- open the app and change the height resolution to 1250. (it worked for me, but make some tests to see if you need to disable a bigger part of the screen to avoid de problem)
This is not the best way to keep using your phone, because you may lost a part of the usable screen, but worked for me.
Thanks!
I workaround this issue avoid using undervoling in the kernel, and avoid lower temperatures in phone, yes as you read ... this issue give my crazy when my phone was to hot and I tried to cold my phone using one ice cube in screen and back, the temperature of the phone down but ghost touches appears again, so played some videos to warm the phone again and dissapear again.
Don't ask me about how it works, or relation with screen, digitizer or battery, I don't understand but help me to workaround the issue.
Related
I am not sure how many owners of the SM-G730A are mobile gamers at all, but maybe some of you have noticed this...
Since the update to Android KitKat 4.4.2 the touchscreen behaves erratically in certain games, primarily FPS shooters. I know it is not an issue with my particular device, goto Google Play and look up Dead Trigger 2. View the reviews for this device model only, you will see numerous complaints beginning after the date the OTA was released (8/27/14) complaining about the touchscreen controls.
I have downloaded the kernel source code from Samsung for both 4.2.2 and 4.4.2. Upon examining the kernel source, the Atmel touchscreen driver has been updated in 4.4.2. I believe this to be what is causing the problem. I am not sure if it is configured incorrectly or if it is just a poor driver. The Jelly Bean driver gave NO issues what so ever. I would revert back to 4.2.2 Jelly Bean if I could. I also compiled a kernel for KitKat which includes the Jelly Bean Atmel driver, however due to the locked bootloader, it does me no good.
What happens is this, you will have two fingers on the screen. Suddenly it is as though you lifted one, even if you are still touching the screen. Touches are erratic for a few seconds after this happens, then touch returns to normal temporarily until it happens again (usually only a few seconds later). This makes using the device for gaming extremely annoying, and difficult. This issue does not occur in normal use, only gaming, where there is rapidly changing multitouch inputs.
If any of you have noticed this, maybe you can contact Samsung/ATT complaining of the issue, if we're lucky maybe a patch will be released. Or it will be fixed in a future firmware update. I already wrote to both, ATT says they will forward the complaint to their management, Samsung has yet to reply.
http://www.samsung.com/us/support/contact / [email protected]
Also, this is a video I created demonstrating the problem. The video includes annotations describing the issue that can only be viewed from PC YouTube.
https://www.youtube.com/watch?v=3FMEPB51Y-4
Thanks for reading.
Has anybody with this device tried a multi-touch test? I'm starting to wonder if it's related to my screen protector. The issue only started after the KitKat update though, immediately after. I do a good amount of mobile gaming or I'd never have noticed it still to this day. Never presents itself outside of fps games.
Best way to check (within multi-touch test app):
Touch screen with two fingers.
Keep one stationary and rapidly slide the other around for a few seconds then stop and lift that finger only.
The stationary touch will act as though you lifted even though you didn't.
Sometimes touches will be erratic for a while if the test is repeated several times.
If anyone tries this please let me know if you have a screen protector or not and how it behaved. Thanks.
Nobody with this device on KitKat is willing to do a multitouch test for me?
All you have to do is turn the phone sideways so the app is in landscape mode, touch with two fingers, one on each side of the screen.
Keep one still, move the other rapidly for a little while then stop, but keep touching the screen.
Does the app show that you lifted the other finger even though you didn't?
I'd appreciate it, trying to narrow it down to a kernel driver issue, or screen protector issue.
https://play.google.com/store/apps/details?id=com.rn.yamtt
quakeaz said:
Nobody with this device on KitKat is willing to do a multitouch test for me?
All you have to do is turn the phone sideways so the app is in landscape mode, touch with two fingers, one on each side of the screen.
Keep one still, move the other rapidly for a little while then stop, but keep touching the screen.
Does the app show that you lifted the other finger even though you didn't?
I'd appreciate it, trying to narrow it down to a kernel driver issue, or screen protector issue.
https://play.google.com/store/apps/details?id=com.rn.yamtt
Click to expand...
Click to collapse
Its the phone mine does these same. Might just be a cheap screen make
Deonta23 said:
Its the phone mine does these same. Might just be a cheap screen make
Click to expand...
Click to collapse
Thanks for verifying. It's not the screen itself from what I can tell. I tried this on Jelly Bean with no issues. I did go through the kernel source for KitKat and believe it is the KitKat kernel touch driver. I am hoping for ATT/Samsung to release a kernel patch. The multitouch was perfect in JB.
so i recently replace my mtxp screen and everything was working perfectly until one day i was watching a youtube video and tried using my navbar buttons and they were unresponsive..did everything from rebooted..clear cache..reinstall rom...same problem..its like the bottom of the screen is unresponsive and only works when screen is locked...
anyone else with the same problem/solution?
Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.
vodanium said:
Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.
Click to expand...
Click to collapse
Hopefully I will figure it out.. It's definitely a software problem triggered by a update or system app.. My work around for now is using a nav bar app from the playstore
vodanium said:
Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.
Click to expand...
Click to collapse
Hopefully I will figure it out.. It's definitely a software problem triggered by a update or system app.. My work around for now is using a nav bar app from the playstore
Hi, I have switched on the "Show touches" feature in the Developer options to see whether the screen is detecting touches in the bottom area of the screen: it actually doesn't. It is not an issue on the lock screen though but it is for the navigation bar. So, it seems it is the hardware that is acting up, after all...
I have found a thread about this issue with a workaround to increase the height of the navigation bar by xposed: https://forum.xda-developers.com/moto-x-style/help/navigation-buttons-issue-t3497985
I'll try either that or by installing a custom ROM that has that option built in - e.g. AICP 12.1 (Android 7.1) seems to have such setting.
https://forum.xda-developers.com/moto-x-style/help/solved-navbar-responding-t3993049
Same problem here - at least in my case also a hardware issue after replacing a broken screen. Thought (as many did) it was software because TWRP, lockscreen etc works, but if you actually try touching only the downmost parts of the TWRP or lockscreen buttons, it won't react. "Show touches" from developer tools also shows touches being registered only just above the normal navigation buttons.
So I had a perfectly fine Motorola MOTO X Style and all of a sudden, without notice, the navigation bar at the bottom stopped responding. I could figure out it wasn't a hardware issue because that part of the screen would still be responsive when the black navigation bar was there.
So i decided to root and unlock my phone and I've been trying to put several roms, i tried with crDroid and with pureXMM from this very same forum , and sometimes it would work and others it just wouldnt. Now i'm up to a point where I installed a new rom and it still doesnt work. i don't get why, it now doesn't work even in the TRWP recovery app. and my latest rom is pure slim (also from this very same forum) and now the whole bottom area won't respond to anything (not even the keyboard space, because I disable the navigation bar and keyboard is pushed down because of the empty space and it just wont work. I have no idea of what could be causing this problem. but it feels as if there is an invisible spacer on top of that bar that impedes the whole bar from working.
i'm so confused, any ideas?
I had a similar issue just recently. Using the developer options I was able to see that the presses under a certain line are not registered anymore. Strangely enough, after charging the phone over night, the issue is gone. I am now dreading its return and start to search for a new phone as it seems from your comments that this is a hardware defect and not a software issue...
troin said:
So I had a perfectly fine Motorola MOTO X Style and all of a sudden, without notice, the navigation bar at the bottom stopped responding. I could figure out it wasn't a hardware issue because that part of the screen would still be responsive when the black navigation bar was there.
So i decided to root and unlock my phone and I've been trying to put several roms, i tried with crDroid and with pureXMM from this very same forum , and sometimes it would work and others it just wouldnt. Now i'm up to a point where I installed a new rom and it still doesnt work. i don't get why, it now doesn't work even in the TRWP recovery app. and my latest rom is pure slim (also from this very same forum) and now the whole bottom area won't respond to anything (not even the keyboard space, because I disable the navigation bar and keyboard is pushed down because of the empty space and it just wont work. I have no idea of what could be causing this problem. but it feels as if there is an invisible spacer on top of that bar that impedes the whole bar from working.
i'm so confused, any ideas?
Click to expand...
Click to collapse
Sounds like it's hardware, try changing size of navbar in custom room to 125% to temporarily solve
Spencervb256 said:
Sounds like it's hardware, try changing size of navbar in custom room to 125% to temporarily solve
Click to expand...
Click to collapse
that's pretty muth the only thing left I can do.
The bottom part of the screen no longer works for me.it was weird because it worked for a starter but then it just stopped working. the first half inch more or less of my screen is senseless
so im having the same problem on my xt1572. Im running Aicp 7.1.2 Navbar suddenkly stopped working. so i went to dev options and enabled show touch on screen and sure enough it didnt recognise touches below the navbar start line. so i did what was suggestedand clean flashed, same problem, and then i increased navbar height, now the navbar is working but the strange thing is the show touches settings is still turned on and however much i increase the navbar height the touch is never recognized beyond the strat of the navbar so im thinking its still a software issue.
viggyv said:
so im having the same problem on my xt1572. Im running Aicp 7.1.2 Navbar suddenkly stopped working. so i went to dev options and enabled show touch on screen and sure enough it didnt recognise touches below the navbar start line. so i did what was suggestedand clean flashed, same problem, and then i increased navbar height, now the navbar is working but the strange thing is the show touches settings is still turned on and however much i increase the navbar height the touch is never recognized beyond the strat of the navbar so im thinking its still a software issue.
Click to expand...
Click to collapse
Beyond the strat? If it's still not showing touches I'd be inclined to say hardware. I don't know what it is, but these screens don't seem to hold up very well..
Spencervb256 said:
Beyond the strat? If it's still not showing touches I'd be inclined to say hardware. I don't know what it is, but these screens don't seem to hold up very well..
Click to expand...
Click to collapse
I am also suffering from this nav bar issue. Tried factory reset, 1st time it solved the problem, but it started again. I reset again, but it didn’t fix.
It seems like the culprit is nav bar. Then is the problem in hardware? Did anyone try replacing the phone screen?
My thought is,
1. Since the nav bar area seems to be causing the problem, it maybe a bug, so software issue.
2. The battery heats up alotttt, which may also cause some issue. And battery is just beneath the screen.
Please if anyone has a solution, please inform. TIA
IftekharAziz said:
I am also suffering from this nav bar issue. Tried factory reset, 1st time it solved the problem, but it started again. I reset again, but it didn’t fix.
It seems like the culprit is nav bar. Then is the problem in hardware? Did anyone try replacing the phone screen?
My thought is,
1. Since the nav bar area seems to be causing the problem, it maybe a bug, so software issue.
2. The battery heats up alotttt, which may also cause some issue. And battery is just beneath the screen.
Please if anyone has a solution, please inform. TIA
Click to expand...
Click to collapse
Some of my friends had this problem too. They had to replace a new battery and some even a new lcd. Battery caused this problem.
https://forum.xda-developers.com/moto-x-style/help/solved-navbar-responding-t3993049
I thought it might be a sensitivity issue because I'm coming from a N6 where I barely touch the screen and it registers. I did some testing and turned on show visual feedback for taps in developer options and I started tapping on the screen in random places every 2 seconds and on average every 5th tap it didn't register and sometimes it's the second and I had issues sometimes where 3-4 taps in a row in different places wouldn't register. For me it's not isolated to certain parts of the screen like many people have found, for example only on edges.
My sample size isn't very much but I've figured out that the majority (or only UI elements because I haven't tested enough) tapping on or around UI elements such as toggle settings in the developer options, any app (swiping/scrolling in apps too) that this issue occurs. When I moved an app icon to create a new screen and started testing I never had any registration issues(visual feedback for taps and long pressing to bring up the wallpapers/widgets/home settings intermittently between taps)
So is this a hardware issue, software UI or maybe a mix of both? I don't know enough about touch screens and android. I don't want to RMA if it's software but I do if it's a hardware issue. Does anyone have any insight on this?
So I did a factory reset and it's working perfectly now. I don't know what was causing it but it's good to know it wasn't hardware
I have the same issue, fingers crossed the upcoming update will fix this.. Mostly its a software issue (or hoping so), but I've seen few complaining about this..
I have the same issue. Its most likely a software issue that can be addressed through an update.
Mine seems to come and go. Sometimes it's fine; sometimes I'm having the same issues you're describing.
I was thinking last night it seemed like every once in a while a double tap is required, after idling for a few seconds. This to me sounds like a driver issue that could be fixed.
Today however I'm thinking it might have something to do with cold dry fingers, as I was having it outside but it's totally fine now indoors.
Can't really put my finger on it yet. Gonna give it a few more days before I think about an RMA.
Any of you guys using SwiftKey beta?
edit: are you on 8.0 or the 8.1 preview?
Just got my xl today and I have this issue. It's just randomly around the screen and not in any specific area.
I believe my phone is not recognizing vertical sliding if it is diagonal, versus the same diagonal slide on my 6p is recognized. Not sure why this is happening but I believe it is intentionally being done because if I touch same spot and closer to vertical up and down, it recognizes it.
Ferenczy68 said:
Any of you guys using SwiftKey beta?
edit: are you on 8.0 or the 8.1 preview?
Click to expand...
Click to collapse
I am using swiftkey Beta on 8.0 and all functioning great
I don't know if this is related but I've been using accubattery and after I did a factory reset I didn't install it at first and everything was working great then I installed it and after awhile I noticed the issue come up again. I uninstalled it about an hour ago and did testing and the issue is gone.
I'm on 8.0
Issues came back even with accubattery uninstalled
I have the same problem. When trying to scroll a web page in Chrome, I have to touch twice to get the touch to register. Also having trouble with the long presses.
I'm on 8.0
I have Swiftkey (not beta)
I do not have Accubattery
I'm having major issues with this all of the sudden today. Something isn't right. Ugh - one issue after another.
I made a video of my issues:
https://www.youtube.com/watch?v=tfnE_Cv-s20
Sometimes, when trying to scroll a web page in Chrome beta, I have to touch twice to get the touch to register. Saw this on 8.0 and now on 8.1.
Neverendingxsin said:
I made a video of my issues:
https://www.youtube.com/watch?v=tfnE_Cv-s20
Click to expand...
Click to collapse
That's horrible. I opened my gboard in chrome and it doesn't do that for me but it will do that swiping/scrolling, randomly typing and with GUI elements sometimes. Multiple times in a row to where i have to just stop tapping and wait a second or two and tap again.
I'm going to try using the 8.1 dev preview to see what happens
I'm having this issue too
Sent from my Pixel 2 XL using XDA-Developers Legacy app
dekciw said:
That's horrible. I opened my gboard in chrome and it doesn't do that for me but it will do that swiping/scrolling, randomly typing and with GUI elements sometimes. Multiple times in a row to where i have to just stop tapping and wait a second or two and tap again.
I'm going to try using the 8.1 dev preview to see what happens
Click to expand...
Click to collapse
I get the same thing while typing, i'll think i tapped something (because I know i did) but it won't register. Extremely annoying and all 3 phones I've gone through had the same issue, getting tired of RMAing
I mainly get this problem with gboard and the home button. It will double click a lot when I only touch once
Sent from my Pixel 2 XL using XDA-Developers Legacy app
I'm also seeing this randomly as well! This is my biggest bug right now...
I installed the 8.1 dev preview and right off the bat it's working perfectly but let's see what happens in the next few hours. I don't understand why it's fine then all of a sudden not. It's completely ridiculous
Make sure you guys are enabling "show taps" under input in the developer options because when you tap and the visual feedback doesn't show then it's not registering. Enabling "pointer location" helps make it more obvious also
dekciw said:
I installed the 8.1 dev preview and right off the bat it's working perfectly but let's see what happens in the next few hours. I don't understand why it's fine then all of a sudden not. It's completely ridiculous
Make sure you guys are enabling "show taps" under input in the developer options because when you tap and the visual feedback doesn't show then it's not registering. Enabling "pointer location" helps make it more obvious also
Click to expand...
Click to collapse
I'm on 8.1 still having these issues
Sent from my Pixel 2 XL using XDA-Developers Legacy app
I've just purchased a Tab S5e but appear to be having some issues with the touchscreen. I first noticed it when scrolling, occasionally the scrolling would stop and the device would click on anything that was under my finger. I also noticed this when playing a game where a finger needed to be held on the screen, it was sometimes appear to the game that my finger was removed.
I recorded a video of what i'm experiencing here: https://drive.google.com/file/d/1-33ixSpHRijjhb8g-MNLvbjMvuPRuGrQ. I did not remove my finger at all whilst drawing in white, but gaps appear.
I guess my question is has anyone else experienced this, or could this be a hardware fault? I thinking of returning this and waiting for the S6e or similar rumoured to be out soon.
Thanks all!
I'm experiencing touch screen problems where I sometimes need to tap the display 3 or 4 times before the screen will register the touch. I've only had mine for a few days but Im thinking about returning as well.
I was going through the threads for the first time to see if there were similar issues reported or tips to minimize the issue.
After switching from the Huawei Mate 20 Pro to the Samsung S10+ and from a Huawei tablet to this I have to say I'm seriously underwhelmed with Samsung.
jhs39 said:
I'm experiencing touch screen problems where I sometimes need to tap the display 3 or 4 times before the screen will register the touch. I've only had mine for a few days but Im thinking about returning as well.
I was going through the threads for the first time to see if there were similar issues reported or tips to minimize the issue.
After switching from the Huawei Mate 20 Pro to the Samsung S10+ and from a Huawei tablet to this I have to say I'm seriously underwhelmed with Samsung.
Click to expand...
Click to collapse
Did you somehow solve the probelm?
k.bergmann2 said:
Did you somehow solve the probelm?
Click to expand...
Click to collapse
Nope. The problem doesn't occur when playing games or using apps that test the display--but does with pretty much everything else. Some apps also have very pronounced jelly effect while scrolling including the Samsung Members App--scrolling through posts has so much jelly effect it makes me feel like I'm going blind.
Earlier Galaxy Tab devices had a calibration setting to adjust touch sensitivity but the type of panel used in the S5e apparently can't be user calibrated. Some people have claimed that the pointer speed setting is the same thing but touch sensitivity and response speed aren't the same thing and increasing that setting to the max didn't improve anything for me. If you want a faster response that's one thing but if the touch doesn't even register in the first place then there isn't anything to speed up.
The game optomizer service running in the background clearly ramps up the kernel when playing games to eliminate or minimize the touch issues and display test apps are treated like games and also get the extra performance boost--but with a locked bootloader I don't think there are any user options besides not purchasing Samsung in the first place.
Would a custom rom solve this?
k.bergmann2 said:
Would a custom rom solve this?
Click to expand...
Click to collapse
I always check before buying a tablet to make sure there is developement of custom ROMs in XDA. And the first thing I do when I get one is to root and install one. Are there still "touch problems" with my ROM? Yes and no. I've noticed with this and other tablets that when the tablet first boots, there can be a lag in touch response. But I don't think it has anything to do with "touch sensitivity". I think the problem is that the OS is still "setting up" and just isn't ready to accept touches. (Try it on a Win 10 box. There is a terrific delay between the time the desktop screen first appears and the time it is ready.) This can also be true of apps. The screen can display before the app is ready for input. IMNSHO, I think some people just love to find reasons to knock "the vendor they love to hate".:crying:
Since I bought this tablet, I noticed that issue, the screen detects the touch, but it does not perform the action I want, open an app, select something,etc. I learned to live with it, but that is annoying !!, I installed a Custom ROM specifically [ROM] [UNOFFICIAL] [gts4lvwifi] [10] LineageOS 17.1 and I can confirm that the issue disappears, the problem for which I returned to STOCK, is the cut down quality of Amazon Prime Video, Netflix, because Widevine Level certification . and now in STOCK, I lost Samsung PASS, because it detects that I have the rooted device. fyi, my model is SM-t720.