yashsingh1/xdaforums huggingface dataset:
[Google Pixel Questions & Answers] fluidfocus:
My Pixel will arrive in a few days, I'm excited. I want root for things like custom firewall, ad blocking, filesystem access - but I need to be able to use Android Pay for work. I've been doing some research on how to make Android Pay work with root and have a couple questions. I'd really appreciate if anyone could help answer these.

First, let me summarize my understanding. Root requires an unlocked bootloader. Android Pay uses SafetyNet to check for both root and an unlocked bootloader. These two things must both be addressed.

To get around the unlocked bootloader check, flash a kernal that's patched to circumvent the SafetyNet check.

In terms of rooting, the most recent and seemingly best method for doing so looks to be ChainFire's SuperSU v2.78 SR4.

Magisk can generally be used to easily get around the *root check*, but probably doesn't work on the Pixel yet.The Magisk developer says it's a work in progress as of Nov. 14, 2016. Technobuzz posted a guide on installing Magisk for the Pixel but in another thread people didn't seem to have much luck with it.

Question 1) Is it correct that Magisk's primary benefit in this case is to allow root to be either restricted from certain apps or to be toggled system-wide without a restart? In other words, I can still disable root directly through the SuperSU program, but without Magisk that then requires a restart.

Question 2) Does the Android Pay SafetyNet check only prevent the addition of cards into Android Pay, or does it also prevent the usage of Android Pay after a card has been added. I ask because I wouldn't mind restarting to disable root when I want to add a card, but I don't want to restart every time I want to simply use Android Pay (and have already added a card).

Question 3) ChainFire notes that suhide does not work on Pixels, nor does it work on Android 7.1 at all. I haven't been able to figure out exactly what suhide does and whether it matters to me. Do I care?

Question 4) In the slightly previous version of ChainFire's rooting (SuperSU v2.78 SR2) he calls out that the kernel must be patched. Sounds like since this doesn't require a kernel recompile that it shouldn't interfere with the custom kernel + SafeNet patch necessary to circumvent the unlocked bootloader check. Right?

Many thanks in advance for taking the time to read and respond.
[Google Pixel Questions & Answers] TonikJDK:
You got the bootloader part right. None of anything else you listed applies to this phone.

Magisk doesnt work on this phone. The versions of SU you mention are the wrong versions for this phone. You need 2.79 SR3. Anything below that and you will bootloop.

There is a thread around here were some folks fot SUHide working for awhile, bit an update or two ago broke that.

I do not believe there is currently any way to get pay to work with root. Google seems to be pretty serious about Pay not working on modded phones.l

---------- Post added at 12:40 AM ---------- Previous post was at 12:39 AM ----------

And to answer question 2, it prevents it from working at all.
[Google Pixel Questions & Answers] fluidfocus:
Thanks for responding. I see your point about SuperSU SR3. SR5 looks like it may work also. I admit that it's still unclear to me what suhide does. Are you saying that without suhide I won't be able to simply check the box within the SuperSU program to disable root and get around the root check (assuming I have patched bootloader also)?
[Google Pixel Questions & Answers] TonikJDK:
Suhide was a project Chainfire did to hide root for Pay. It was a separate install that modded it to hide it. Currently not working on this phone.

2.78 SR5 will not work.

There is no disable root checkbox that i can find on mine. Perhaps something that was in previous versions.
[X Style (Pure) Q&A, Help & Troubleshooting] Bill720:
Now that I've got the Moto X Pure Edition activated, I've been able to work out some of the kinks inherent using it as a daily driver. One noteworthy issue that remains is an odd bug where the device will completely lose connection to the Internet on both a WiFi and cellular data connection, usually after transitioning between types of connections. When this happens, an exclamation point is displayed next to the icon representing whichever connection is currently active and nothing is able to transmit data to or from the Internet or even my local network.

Rebooting the device always fixes the problem, but this issue is materializing a bit too often for my liking, which is usually once every time that I return to a WiFi network after being disconnected from one for some time (more testing may have to be done to confirm exactly what triggers it).

The device is running the stock rom (rooted) and the stock kernel along with the usual tweaks (ad-blocking, Xposed framework, audio fixes, etc.). Anybody seen this before or know what might be causing it?

UPDATE (3/1/2017)

Figured it out! :o The problem appears to have been caused by my failure to whitelist certain applications in PowerNap. After following the instructions found in the Moto X Pure Edition power optimization thread, the problem appears to have vanished. I don't know if it was the Google Services Framework, JavaTcmdHelper, Android System, or some combination of those that needed to be whitelisted, but the problem has vanished. At least one of those must be responsible for verifying the validity of an Internet connection in sleep mode, which would cause the device to become confused when it would wake up with a different connection that it hadn't verified (that's my theory at least).

At any rate, it is no longer an issue. :D

Update (Later on 3/1/2017)

Well, it looks like it might not be fixed so well after all. A couple hours after arriving home today, I went to use the device and saw the dreaded "!" next to the network indicator. Still, two days is longer than it's ever lasted before. I've cleared the cache and dalvik/ART cache to see if something in there might be gumming it up and will add another post to this thread if the problem returns.
[X Style (Pure) Q&A, Help & Troubleshooting] Bill720:
Still an issue

Looks like it might not be fixed after all. I lost connection again the other day in a parking lot and once more today after getting home. Any ideas as to what could be causing this?
[X Style (Pure) Q&A, Help & Troubleshooting] inkdaddy66:
I just recently got my x pure. I've seen this issue on mine too.
[X Style (Pure) Q&A, Help & Troubleshooting] Bill720:
Another one!

Interesting. Are you running the stock Rom? Rooted? Amplify/Greenify/PowerNap?
[X Style (Pure) Q&A, Help & Troubleshooting] inkdaddy66:
I'm unlocked and rooted. Running validus 7.1.1 ROM.
[X Style (Pure) Q&A, Help & Troubleshooting] Bill720:
does your configuration look anything like this?

That too is interesting. I'm running the stock Rom, (rooted) so we can probably eliminate that as a potential cause. Given how little reference there is to this on the web at large, the problem is probably caused by a common app or setting (or some kind of unfortunate combination) running on both of our phones.

All we need to do is figure out what kind of "unusual" stuff our devices have in common. I'll rattle off a list of software and settings that might be out of the ordinary or network-related; you tell me if you're running anything like it on your phone.

AdFree

A.R.I.S.E. audio

FolderSync

Ice Box (Motorola Update Service is the only frozen app)

TOTAL Wireless My Account App

Pebble, MyTracks, and Pebble MyTracks

SlingPlayer (this one sometimes wakelocks)

Titanium backup (I tried restoring some WiFi access points once, but it didn't work)

Xposed Framework with Amplify, Greenify, and Power Nap installed and configured as instructed in the Moto X Pure Edition battery life guide thread OP. I've also got MinMinGuard and YouTube AdAway.

As far as settings go, I've not got much in the way of unusual configurations. I enabled the system UI tuner to get the battery percentage and the extended developer options to try out multi-window, (and to change the animation scales to .5X) but everything in there is still pretty much stock.

Does your configuration have anything in common with mine?
[X Style (Pure) Q&A, Help & Troubleshooting] Bill720:
Close, but no cigar

It got almost 8 days this time before it happened again. I thought that maybe switching to the legacy DHCP client had done the trick, but that was apparently not the case. Any ideas as to what could be causing the issue or how to fix it?

Or, if you're having the same problem, can you look at my list in the previous post and tell me if any of the software or settings are similar so that we can narrow down the cause?
[X Style (Pure) Q&A, Help & Troubleshooting] aybarrap1:
I have had this problem appear about three times over my 13 months of ownership and all three times was when my bootloader was still locked (obviously running stock not rooted). Never found a solution except to reboot.i only unlocked and rooted my device about a month ago.
[X Style (Pure) Q&A, Help & Troubleshooting] Bill720:
Anything familiar?

Interesting. Between that, my findings, and the fact that [MENTION=3247858]inkdaddy66[/MENTION] was having the problem on a non-Motorola Rom, I want to think that we can eliminate the Rom software as a cause. Did you see any familiar software on my "potential troublemakers" list up in post 6? I'm thinking that if we can find a common program or workflow, then we'll be able to narrow down the cause of the problem.

In the meantime, I'll try posting in the general Android troubleshooting forum here on XDA and see if anybody there has seen the problem or has any troubleshooting tips.
[X Style (Pure) Q&A, Help & Troubleshooting] aybarrap1:
Nothing used from your list except system UI tuner when I experienced the problems. That would leave either a ROM and/or hardware issue IMO.
[X Style (Pure) Q&A, Help & Troubleshooting] Bill720:
Cause and effect differential diagnosis

Hmmm... That's also interesting, but I just don't see how system UI tuner could be harming anything. Do you have any other apps or settings at all that you think could be causing the issue?

If this were anything other than my primary, I'd hard reset and troubleshoot that way, but I don't exactly have the time to pull the rug out of an otherwise-working setup right now, so this is going to have to be done the hard way (or, in the case of hardware glitch, lived with).

At any rate, I discovered a new symptom earlier in the week. This time, Internet connection was lost, but only for WiFi, so the connection would actually fall back to Cellular and still continue to work. As before, toggling the connection had no effect, but rebooting the device "fixed" it. I thought maybe it was a fluke, since we'd had an AP hiccup over the weekend, (I refuse to reboot that thing because I'm going for an uptime record) but it happened again on Wednesday, so I'm not sure what to make of it.

Side-issue aside, I'm beginning to wonder if it's some kind of combination of network behavior and usage pattern that brings the issue about. It seems like if I stay within range of the WiFi network, no issue develops, but if I move out of its coverage and don't touch the phone for a while, that allows for ideal conditions under which to replicate the problem (sometimes). I haven't nailed down a consistent pattern yet, but the problem does emerge more often when I'm returning home than at other times. Any thoughts?

Update (3/24/2017; 12:32PM)

Scratch that last part about the issue only being triggered upon "arriving home." The problem happened again this morning, in the same general area. First, no WiFI, then, after resetting the connections, no cellular either. I captured a LogCat before rebooting this time though. Anyone want to take a crack at sifting through that to see if it offers any clues? :D
[X Style (Pure) Q&A, Help & Troubleshooting] pizza_pablo:
I lose cellular data, from time to time, I don't kow if I'm losing WiFi capability also, because I'm on the road when this happens.

It takes a reboot or switching in and out of airplane mode to regain data.

I have had this happen on TruPureXMM ROM and stock-rooted Marshmallow.

I have not spent much time on stock-unrooted, so i don't know if it would happen then, also.
[X Style (Pure) Q&A, Help & Troubleshooting] Bill720:
Possible fix

Just to follow up on this again, I have finally reached the eighth day of uptime without the problem materializing, which is the longest that I was able to go before without it happening. This time, I went in to the developer options and disabled "Cellular data always active." I'd give it another couple days to know for sure, but if this sticks, then I think we might've found the fix!

If your trouble is isolated to just one connection and/or cycling the connection brings it back, then the issue you are experiencing is unrelated to the one described in this thread.
[X Style (Pure) Q&A, Help & Troubleshooting] acejavelin:
Cellular data always active should never be on (it's disabled in stock rom), except if you have VoLTE only with no fallback to 3G or 2G (Jio is the only provider that comes to mind, but this phone doesn't support their service anyway) or otherwise unusual scenarios I can't really think of.
[X Style (Pure) Q&A, Help & Troubleshooting] pizza_pablo:
Huh, and CELLULAR DATA ALWAYS ACTIVE (for faster network switching) sounds like such a good thing.

Mine was selected on.

My loss of data happens in the same spot, usually, but is not leaving wifi. Perhaps it is a tower to tower handoff spot.

I turned it off. Time will tell.

Thanks, fellas!
[X Style (Pure) Q&A, Help & Troubleshooting] aybarrap1:
Always on is not necessarily a good thing. Reality is that when you lose or turn off WiFi, mobile data should only be delayed only by a second or two. There is no real benefit to having it on except for maybe VOLTE.
[X Style (Pure) Q&A, Help & Troubleshooting] acejavelin:
Actually, it's a battery killer more than anything else... It keeps cellular data active even when on WiFi.

It is possible it's a tower thing though. I have noticed at this one hotel I stay at frequently people tell me they call and it rings or just goes to voicemail even though I have good signal. After investigating it a bit, I'm in a spot that has nearly identical signal strength from 3 towers and it's a metro area so there are 4+ bands accessible... I've seen times watching LTE Discovery where it keeps switching bands and towers for 30 to 120 seconds or so, like it can't make up it's mind what to talk to because it's confused, then it locks on for a while before it starts it's cycle again. During those cycles I think is when people​ can't call me, can't really say if it affects internet or not since I tend not to use my phone too much in the evenings when I'm on the road (usually on laptop).
[X Style (Pure) Q&A, Help & Troubleshooting] Bill720:
Uptime record, but... it's back

Interesting. I thought for sure that I had the default settings checked in there, but maybe I did change it early on and just forgot. Either way, waiting an extra five seconds to establish a data connection isn't that huge of a deal for me, so I'll leave it off anyway in exchange for battery life when the signal's poor.

At any rate, however, the problem has returned. I was just a few hours short of 9 days of uptime and really thought that I was out of the woods with this problem, but it has returned once again upon returning into range of the home access point. Looks like we're back to the drawing board on this one.

So you're having the same problem too? That makes at least four of us now. Do you mind sharing what Rom and flashed tweaks (Xposed Framework, A.R.I.S.E. audio, root, etc.) you're using as well as any unusual software or settings? Anything in common with my list on page 1?
[X Style (Pure) Q&A, Help & Troubleshooting] pizza_pablo:
I think we've established that my issue is different, but it has occurred on TruPureXMM and stock but rooted Marshmallow, both with Substratum, Xposed (Gravity Box only) and Viper Atmos.

Same as you =Titanium Backup
[X Style (Pure) Q&A, Help & Troubleshooting] Bill720:
*another* new strategy (sigh)

For this week's shot in the dark, I'm going to try manually switching WiFi off before I leave anyplace covered by an access point. Since the problem seems to occur most often when connected to WiFi or when connecting to it, maybe this will make some kind of a difference.

I see now; my mistake.
[X Style (Pure) Q&A, Help & Troubleshooting] Bill720:
Leaving WiFi off = no good; shots in the dark welcome

Ugh... Ran into the issue again today, even with WiFi left off on my way home. Once again, I left the phone in my pocket for a while after returning back and when I went to use it, I saw that exclamation point and knew that it would manage to spread to the WiFi connection upon enabling it.

Since we can't nail down a software cause, I'm going to try a behavioral adjustment in the form of immediately using the phone upon returning home, since this is where the issue comes up most frequently (although I'd have to collect some more experiences in order to know for sure).

Any other suggestions are welcome; even shots in the dark. I'm seriously starting to run out of ideas at this point. For example, I sometimes use "Do not disturb" mode, the conclusion of which occasionally coincides with the materialization of the problem. Anybody else use "Do not disturb" mode?
[X Style (Pure) Q&A, Help & Troubleshooting] pizza_pablo:
I have four DND automatic rules and sometimes use it manually.
[X Style (Pure) Q&A, Help & Troubleshooting] Bill720:
Happened again

Got the issue again today, but this time I caught it "as it happens" (as I have once or twice before). I woke the phone up to use it and saw the exclamation point over the WiFi signal strength indicator, but was still able to use the LTE connection. After resetting the cellular connection, it also stopped working.

Does anybody have any ideas as to what could be causing this? I'm even accepting complete and total shots in the dark at this point. Hard resetting and starting from scratch won't be an option right now as this is my daily and I don't have enough spare time to wipe this phone and try again, so my only options are to troubleshoot "in-place" or to acquire a temporary phone so that I can hard reset and properly troubleshoot this frustratingly intermittent problem.
[X Style (Pure) Q&A, Help & Troubleshooting] pardus:
This happens to my v7.1 Nougat Galaxy Note 3 all the time and has happened once or twice with my X Style. The old Note 3 does it when driving anywhere as it changes cell towers, irritating as I'm using it for navigation only. With the Style it has only happened a few times. In both cases an Airplane mode toggle fixes it but on the Note 3 it happens every day. I thought it had something to do with the phones radio firmware. I then found a "fix" on a oneplus forum that advocated this:

"Use android terminal emulator to enter in the below codes.

su

settings put global captive_portal_detection_enabled 0

reboot"

This seems to have worked as the exclamation mark has disappeared but sometimes it still has no signal and requires the Airplane Mode toggle to get the LTE/4G/3G mark back.
[X Style (Pure) Q&A, Help & Troubleshooting] acejavelin:
All you have done by doing this turn off the internet connection detection... It doesn't fix anything, just hides the problem.
[X Style (Pure) Q&A, Help & Troubleshooting] pardus:
Thought something like that, so what's the solution?
[X Style (Pure) Q&A, Help & Troubleshooting] somecro:
There are a few options in "Developer Options" page in "Settings".

1. Aggressive Wi-Fi to Cellular Handover

2. Cellular Data Always Active

If you don't have Developer Options just google how to enable it. Try this if you haven't and see if it works.

I had this problem also but it went away when I uninstalled Gravity Box from Xposed. Haven't had an issue since.
[X Style (Pure) Q&A, Help & Troubleshooting] acejavelin:
I have never seen either of this options fix anything, aggressive handoff always made things worse, and cellular data always active is only intended for when connected to WiFi w/o internet or a VoLTE only service, otherwise it's just a battery drainer.
[X Style (Pure) Q&A, Help & Troubleshooting] Bill720:
No dice

I tried messing with both of those options, but it didn't make much (if any) difference.

If you're able to recover by toggling flight mode or resetting the connection, then that's not the same problem. In this state, no amount of toggling anything will allow the device to establish any kind of network connection (WiFi or cellular) until the phone is fully rebooted.

At this point, the problem has me so intrigued that I'm considering buying another Pure Edition just so that I can have a platform off of which to troubleshoot while not interfering with my daily. That, or getting a cheaper (but still usable) phone to daily while I hard reset and troubleshoot the crap out of this phone.
[X Style (Pure) Q&A, Help & Troubleshooting] Bill720:
Ready to give up on this...

I'm at whit's end with this thing, so I tried that trick for disabling captive portal detection, and that actually does get rid of the exclamation point, but as [MENTION=2001582]acejavelin[/MENTION] pointed out, it only masks the underlying problem; the Internet connection is still down globally. No amount of toggling or switching between connections fixes that.

At this point, unless anybody has any other suggestions, I'm going to give up and just temporarily use another device as my daily while I hard reset the Moto X and start over from scratch.
[X Style (Pure) Q&A, Help & Troubleshooting] pizza_pablo:
I searched, but didn't find....

Have you tried reflashing (or whatever the proper term is) the modems, with the following fastboot commands?

fastboot flash modem NON-HLOS.bin

fastboot erase modemst1

fastboot erase modemst2

I'm pretty sure that it won't harm anything, if it's not actually the fix and you can do this without factory reset.
[X Style (Pure) Q&A, Help & Troubleshooting] Bill720:
Fingers crossed!

That sounds like as good of an idea as any. I've followed the steps and rebooted the device with no negative side effects so far. I guess we'll find out within the next 5-10 days if that actually did the trick or not. Thanks for the suggestion.
[X Style (Pure) Q&A, Help & Troubleshooting] Bill720:
Interesting development

Just to follow up, it appears as though flushing the radio/modem didn't solve the problem, but I did collect some more data surrounding the issue. Yesterday, I took the Pure Edition up north for the first time and was able to not only trigger the problem, but got it to happen no fewer than five times in one day simply by being in and driving through an area with lower-than-average signal quality. The phone was bouncing all around between LTE, eHRPD, 1xRTT, and even no signal. What usually takes about a week to happen at home took just hours (sometimes even only a matter of minutes) to achieve up north.

With that said, I think I'm going to continue with the original plan to hard reset and try again, unless anybody has any other ideas.
[X Style (Pure) Q&A, Help & Troubleshooting] Bill720:
Hard reset; problem should be solved, but time will tell

Well, I took the plunge and started over today. I reflashed the unmodified stock Rom and then accepted the security updates to get to the December 2016 stock release before rooting and restoring all of my data. Just in case the issue was caused by an application, I've only restored my core software load. This includes The Xposed Framework and ad blocking, but not any of the battery life tweaks because I want to first see how the battery life is without them (in addition to ruling them out as a cause of the problem in case the bug comes back).

Hopefully the Internet connection issue is gone for good this time. I still would've liked to have known what the underlying cause was.
[X Style (Pure) Q&A, Help & Troubleshooting] pizza_pablo:
What was the last official, stock security update, your MXPE was on, prior to the reflash?