Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sometimes long press on BACK button to launch Google Wallets feels like a long time to hold down #15

Open
ZainAjam opened this issue Aug 29, 2022 · 5 comments

Comments

@ZainAjam
Copy link

ZainAjam commented Aug 29, 2022

First of all. Thank you so much for making this app.

The issue I am raising here is that sometimes I need to hold down on the BACK button for about 5 seconds to get Google Wallet to launch. Other times it launches in 1 second. Can the long press duration be set to 1 second all the time? It is hard to get used how long to hold down when it is different every time.

@devanteweary
Copy link

devanteweary commented Sep 3, 2022

Hey, I just set up GW4Remap on my Watch4 yesterday.

The first time, it was just as quick as stock.

I've rebooted since then and now both buttons take a few seconds of holding down to register.

edit a couple minute later ha:

So right after I typed that, I tested it and it was still delayed.
Then I went into the settings and disabled mobile data since I don't have the service anyway, then I tested it again for fun and it was quick as can be.

THEN I tested it again and it was laggy again. So I kept pressing the buttons and holding them down and the speed is varied. So I don't know WHAT is going on!

@EdisonChangForWork
Copy link

... Then I went into the settings and disabled mobile data since I don't have the service anyway, then I tested it again for fun and it was quick as can be.

THEN I tested it again and it was laggy again. So I kept pressing the buttons and holding them down and the speed is varied. So I don't know WHAT is going on!

I've followed your pattern and the same situation happened.
Hope the developer would fix it in the released 2.0 version.

@devanteweary
Copy link

Well since then I switched to a non-LTE watch and it's still the same.

However, I find that if I hold it a couple of seconds then let go, then wait a couple of seconds, then hold it again, it usually works.

@gudenau
Copy link

gudenau commented Apr 22, 2023

There is a pretty massive and random delay that I'm experiencing as well. I know you can't see when I'm pressing the back button in the video, but I'm doing it as soon as I exit Google Pay.

Sorry about the awful video editing, I did it on my phone and it only lets me edit the entire video instead of sections of it.

watch_screen_recording.2.mp4

@Bingblop
Copy link

Bingblop commented Jun 16, 2023

The delay is unavoidable. Since the new method of relies on the logcat to detect when button is pressed, it has to wait for the logcat to update and the app to receive the data. Dev addressed this somewhere but basically it seems to update around every 5s. So if you press button when watch is nearing 5s update, it'll be quick, otherwise you could wait the full 5s or more.

The only way around this is to download the previous version of the app that launches over Samsung Pay or Power Menu. You'd have to redownload Samsung Pay as well but through this method, it's almost instant. Just have to deal with with the nuance of launching over something else first. I personally think this is the lesser of two evils because the logcat method can feel quite long when you're trying to pay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants