[ROM][BULLHEAD][Marshmallow 6.0.1]Cataclysm for Nexus 5X[Jan 06 - Stable]

[nathanchance]

OK. Thanks for the info. I'm running on 2.61 and it added just fine. But I wasn't able to pay with it at Best Buy.

It did however work just fine with the same card before I rooted.

I was thinking maybe an app I have broke it. Would "naptime" break it?

Also, just wanna say that this ROM is probably the best I've ever used on an Android device. Thank you to the OP for this.

It is possible. I have heard Greenify may break it as well. Any other mods you have installed lately?

 

[knipp21]

No nothing.

Interesting though.. I just deleted my card and re added it (while rooted) and ran "safety net check" and now it passes..

Edit:

I did delete titanium and reboot. I think that fixed it

 

[ibilln]

Nope, if you can set up Android Pay, you should be able to pay. However, some people have said that some payment machines don't really work well with Android Pay (I'll see if I can find a link in a bit).

I'll raise you a nope. When you install a systemless SU, it will write, among many other things, an /su/xbin-bind. With that you can add cards to AP, since /system was not modified, but AP won't actually work without deleting xbin-bind.

Wait - you have the latter in your guide, which is how I know about it. So, um, ??.

The reason for writing the xbin-bind directory to /su in the first place is unknown to me. I'd try to get and read @Chainfire 's code, but I'm of course too lazy.

More generally, there are at this point various combos of kernel/su/rom. Using the wrong combo, or the right combo in the wrong sequence, can lead one down a bogus path. One has to be quite careful and read a lot of the material on the kernel one wants to use, the rom, and esp the stuff about SU to finally get the gist.

EG, one should read your stuff.

 

[nathanchance]

I'll raise you a nope. When you install a systemless SU, it will write, among many other things, an /su/xbin-bind. With that you can add cards to AP, since /system was not modified, but AP won't actually work without deleting xbin-bind.

Wait - you have the latter in your guide, which is how I know about it. So, um, ??.

The reason for writing the xbin-bind directory to /su in the first place is unknown to me. I'd try to get and read @Chainfire 's code, but I'm of course too lazy.

More generally, there are at this point various combos of kernel/su/rom. Using the wrong combo, or the right combo in the wrong sequence, can lead one down a bogus path. One has to be quite careful and read a lot of the material on the kernel one wants to use, the rom, and esp the stuff about SU to finally get the gist.

EG, one should read your stuff.

Actually you can't even add a card to Android Pay without removing /su/xbin_bind. If it comes back (like after a SuperSU update), your card will still be available but you won't be able to pay because SafetyNet is still in effect.

/su/xbin_bind is a symlink to /system/xbin so that poorly coded root apps (that make hardcoded calls to the su binary) can still work.

All of the SuperSU stuff is definitely a lot to read. New technology and all haha.

 

[ibilln]

Actually you can't even add a card to Android Pay without removing /su/xbin_bind. If it comes back (like after a SuperSU update), your card will still be available but you won't be able to pay because SafetyNet is still in effect.

Coulda sworn I added cards w/o removing xbin-bind - long ago, in ancient times - Ie, about two weeks back.

/su/xbin_bind is a symlink to /system/xbin so that poorly coded root apps (that make hardcoded calls to the su binary) can still work.

Good to know!

 

[knipp21]

I'll raise you a nope. When you install a systemless SU, it will write, among many other things, an /su/xbin-bind. With that you can add cards to AP, since /system was not modified, but AP won't actually work without deleting xbin-bind.

Wait - you have the latter in your guide, which is how I know about it. So, um, ??.

The reason for writing the xbin-bind directory to /su in the first place is unknown to me. I'd try to get and read @Chainfire 's code, but I'm of course too lazy.

More generally, there are at this point various combos of kernel/su/rom. Using the wrong combo, or the right combo in the wrong sequence, can lead one down a bogus path. One has to be quite careful and read a lot of the material on the kernel one wants to use, the rom, and esp the stuff about SU to finally get the gist.

EG, one should read your stuff.

I'm running 2.61 myself. Not to sure what broke it on my part.

I have a month to use it 10 times and get a free Chromecast. So I was just curious for any new information anyone might have.

 

[Atemi1337]

Not sure if I'm oblivious to the post, but does anyone else on Verizon have an issue with keeping lte/data enabled while on a call? Even with HD calling enabled?

 

[nathanchance]

Hey guys, I just updated my guide linked in my signature. I cleaned up the rooting section (made it a little less dense and provided a clear Android Pay path for those who care). Also, since Franco is soon switching to an AnyKernel format (already done on the Nexus 6 with r42, soon to be for all of his other devices), the vast majority of kernels do not include a ramdisk/full boot.img. This allows me to standardize kernel install instructions for both system and systemless installs (you should still always check with your kernel developer for their precise process but this process will apply to the vast majority of them). Let me know if there are any issues as I did all of my threads all at once so I could have goofed somewhere.

 

[jawnah]

Not sure if I'm oblivious to the post, but does anyone else on Verizon have an issue with keeping lte/data enabled while on a call? Even with HD calling enabled?

I use the phone on Verizon but I can't say I have payed any attention. I will try to check next time I am in the car.

Sent from my Nexus 5X using Tapatalk

 

[k.s.deviate]

Random little thing that happens every once and a while. Using fingerprint to unlock the notification shade will be pulled down when it unlocks. Not all the time, but definitely happens after purposefully locking the device knowing the shade is up. Anyone else notice this?

Clean install of latest update all proper files installed prior. (Vendor, bootloader etc)

 

[nathanchance]

Random little thing that happens every once and a while. Using fingerprint to unlock the notification shade will be pulled down when it unlocks. Not all the time, but definitely happens after purposefully locking the device knowing the shade is up. Anyone else notice this?

Clean install of latest update all proper files installed prior. (Vendor, bootloader etc)

See this post and the one he is quote..

 

[k.s.deviate]

See this post and the one he is quote..

Thanks, that helps. Search wasn't my friend.

 

[PiousInquisitor]

jk

 

[Steve46xda]

Hi guys, can you please tell me what should I do if I want to increase my font dimension? I noticed that the when I write sms or whatsapp or other stuff, the letters are too little and difficult to see.
Thanks in advance!

 

[PiousInquisitor]

Hi guys, can you please tell me what should I do if I want to increase my font dimension? I noticed that the when I write sms or whatsapp or other stuff, the letters are too little and difficult to see.
Thanks in advance!

Settings, Display, Font size

Sent from my Nexus 5X using Tapatalk

 

[Steve46xda]

Settings, Display, Font size

Sent from my Nexus 5X using Tapatalk

I am terribly ashamed!! I dealt with governor setting, frequencies, smart radio, permissions, etc...and then I was not able to do something so simple...maybe because it was so simple that I didn't even think that there could be a stock setting for this thing.
Anyway, thank you!

 

[kristof95]

Great features, I really appreciate this "ROM".

I have one different behavior from pure stock and I have trouble to understand whether there is an option to disable it or not.

In pure stock rom, when I receive a notification, the notification light pulses. If I turn the screen ON and stay on the lock screen but does not dismiss the notifications, the notification light doesn't pulse anymore.

Here the notification light is constantly pulsing until I actually dismiss or read the notification. Any way to turn this behavior back to stock?


Thank you!

 

[asqwrd]

is there away to keep persistent notifications from showing up again after being blocked in settings. Sim toolkit ignores the setting and comes back after awhile

 

[AllusionPDX]

Is there a way to enable the notification light to stay on while charging?

 

[till22]

Is there a way to enable the notification light to stay on while charging?

If I remember correctly it's in "Notifications" - but it is somewhere in the settigns, I'm sure of that