Loyalty card app that presents a scanable bar code ?

[Jeremy8000]

+1 for Stocard. Also compatible with Android Wear, so you can just use the watch.. though I do get some funny looks at Starbucks!

 

[N4Newbie]

@N4Newbie - that is odd. I have it setup on my Nexus 6P, and I too have the Oreo 8.1 beta, but it runs just fine for me at any grocery POS (I'm in the St. Louis, MO area). When it reads, the image of the credit card I have it tied to appears, with the Android guy animating (and chimes) when it goes through. I'm assuming a CC is setup (and confirmed) on your Android Pay?

Edit: the only oddity I get is when occasionally some POS will ask for my CC pin (for Debit), but that's it.

I think it had something to do with my disabling all security on my phone and then re-enabling it. From what I have read elsewhere, that can break Android Pay's security model.

Based on what I read, I cleared Android Pay and uninstalled it, cleared my phone's security again, and then started from scratch by reinstalling Android Pay and following along when it prompted me to setup security on my device.

I'll post back when I find out whether it works or not.

 

[jsarino]

^^^Yeah, keep us posted!

 

[N4Newbie]

^^^Yeah, keep us posted!

Nope. Still didn't work.

Unlocked the phone with my fingerprint, held it to the terminal, it beeped and asked for my pin or fingerprint again, and then I had to hold it to the terminal again.

 

[jsarino]

Nope. Still didn't work.

Unlocked the phone with my fingerprint, held it to the terminal, it beeped and asked for my pin or fingerprint again, and then I had to hold it to the terminal again.

I suppose my next question then is did you unlock the bootloader? I know that doing that will mess up Android Pay's functionality.

 

[N4Newbie]

I suppose my next question then is did you unlock the bootloader? I know that doing that will mess up Android Pay's functionality.

No, I did not. In fact, in another thread I specifically pointed out that my biggest reason for not unlocking the bootloader is the fact that it breaks Android Pay.

I have another thought but it will have to wait for my next grocery run to be tested.

 

[jsarino]

No, I did not. In fact, in another thread I specifically pointed out that my biggest reason for not unlocking the bootloader is the fact that it breaks Android Pay.

I have another thought but it will have to wait for my next grocery run to be tested.

Geez, don't you sleep? Post up what you tried and report back!

 

[N4Newbie]

Geez, don't you sleep? Post up what you tried and report back!

Sleep? Haven't got time for that.

 

[N4Newbie]

So, a quick update...

I really, really, thought I found the problem when I read that specific types of Smartlock settings can screw with Android Pay. In particular, I read that "On body detection" was considered a no-no because, as one Googler said, a bad guy would be able to just brush up against you with a device in his pocket and steal thousands from your default credit card if your device was unlocked while on your person. Made sense and, since I had only recently enabled On Body Detection I thought that might be it. But no-go.

Then I thought, well, maybe Trusted Voice? I had also recently enabled that (never bothered with it before). So, I disabled it and still no-go.

I have one last hope right now - see this thread: https://forums.androidcentral.com/g...-phone-number-did-you-just-sign-new-post.html

Perhaps that was somehow messing with Android Pay as well? I'll find out on my next grocery run.

 

[jsarino]

That is an odd solution that fixed Project Fi for you. It was also specific to the Pixel 2's...no such issue with my other phone (Nexus 5X) on Fi.

 

[N4Newbie]

That is an odd solution that fixed Project Fi for you. It was also specific to the Pixel 2's...no such issue with my other phone (Nexus 5X) on Fi.

Ugh. Android Pay still doesn't work without forcing me to enter my pin each time, even though the phone is already unlocked.

 

[jsarino]

Ugh. Android Pay still doesn't work without forcing me to enter my pin each time, even though the phone is already unlocked.

I forgot if I asked this (too lazy to look back ), but did you clear the data in Android Pay itself and re-set it up?

 

[N4Newbie]

I forgot if I asked this (too lazy to look back ), but did you clear the data in Android Pay itself and re-set it up?

Yep.

So, I just finished a long chat with Google support and the one thing of interest that came up (after he did a separate chat with higher-tier support rep) was to check Settings -> Security & location -> Screen Lock (PIN) -> Gear icon. "Automatically lock" was set to 5 seconds after sleep - which probably defaulted to that after I disabled and re-enabled security last week, He told me to change it to at least 15 seconds but I went with one minute because I am pretty sure that is what I have always used in the past.

He thinks this change is going to fix it. Guess I'll have to stop at the grocery store again...

 

[jsarino]

Yep.

So, I just finished a long chat with Google support and the one thing of interest that came up (after he did a separate chat with higher-tier support rep) was to check Settings -> Security & location -> Screen Lock (PIN) -> Gear icon. "Automatically lock" was set to 5 seconds after sleep - which probably defaulted to that after I disabled and re-enabled security last week, He told me to change it to at least 15 seconds but I went with one minute because I am pretty sure that is what I have always used in the past.

He thinks this change is going to fix it. Guess I'll have to stop at the grocery store again...

While you're there, get me a case of beer...I ran out at home. Seriously though, hope that works!

Edit: on mine, it's set to 5 seconds. But, I'm also using Smart Lock, so Android Pay stays unlocked.

 

[N4Newbie]

While you're there, get me a case of beer...I ran out at home. Seriously though, hope that works!

Edit: on mine, it's set to 5 seconds. But, I'm also using Smart Lock, so Android Pay stays unlocked.

But, I am not using any Smart Lock options any longer, either.

Bad news that you are set to 5 seconds and it is working fine for you...

 

[jsarino]

But, I am not using any Smart Lock options any longer, either.

Bad news that you are set to 5 seconds and it is working fine for you...

My Pixel 2 XL arrived this afternoon...of course, while I'm at work. I should've had it shipped at work instead, but anyways...

When I set mine up, I'm going to do the same settings like I did with my 6P, including the Smart Lock setup. Could your issue be a Pixel-specific issue? I'm going to find out soon enough, and, uh, get some beer.

 

[N4Newbie]

My Pixel 2 XL arrived this afternoon...of course, while I'm at work. I should've had it shipped at work instead, but anyways...

When I set mine up, I'm going to do the same settings like I did with my 6P, including the Smart Lock setup. Could your issue be a Pixel-specific issue? I'm going to find out soon enough, and, uh, get some beer.

Just to be clear, I don't care for beer at all. I'll have one or two socially when necessary to be "one of the guys" but otherwise I prefer bourbon on the rocks.

As to the Android Pay problem, I don't think it is specific to any particular device or even configuration, but Googling shows that it affects a fair number of people and the solution is always difficult to find.

 

[jsarino]

Just to be clear, I don't care for beer at all. I'll have one or two socially when necessary to be "one of the guys" but otherwise I prefer bourbon on the rocks.

As to the Android Pay problem, I don't think it is specific to any particular device or even configuration, but Googling shows that it affects a fair number of people and the solution is always difficult to find.

Heh, beer is my go-to when I'm unwinding. But I do like a good bourbon too, and drink wine on occasion. If I want to take the effort to do it myself when home (or find a bartender willing to mix it when I'm out), I like the Vesper martini.

Back to subject, that's always the tricky thing about bugs, especially if it's not tied to a specific device. I hope your latest tweak takes care of it this time.

 

[loqk]

I haven't seen the explanation yet, but I haven't read the whole thread.

The company that made beep n go published a paper explaining the use of the infra red proximity sensor receiver on some smart phones to read a barcode scanning laser and write a return signal via the proximity sensor transmitter. When using beep n go, you need to hold the phone where the scanner can see the proximity sensor, not the screen.

Beep n go was then sold to Samsung and integrated into Samsung pay as Samsung did already use this type of proximity sensor.

I assume the technology is patented, or the pixel phones use a different method to detect when the phone is next to your ear, or both.

Either way, my new pixel can't use beep n go while my old Samsung wrote barcodes to laser based readers like a champion.

I originally thought something like this might be possible, searched and found the paper and read in that paper that an app was being produced with the help of Samsung. I then searched for and found the app.