-
Notifications
You must be signed in to change notification settings - Fork 48
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
RAB will attempt to walk #57
Comments
Happens to me with PGSHARP. It keeps doing subtraction. Can't catch Pokemon. Saying "None" does not throw the poke ball. Can't catch Pokemon. |
Maybe you should state your configuration including the brand of phone that you use. I had the same problem with you and I am using Samsung, in which I solved it by turning off the gesture mode. |
I fixed this by changing the gesture features in the phone (just by gesture), with buttons didn't work and i had the same behavior Poco F2 Pro working |
I have a Samsung J7 SM-J710MN. Using android 8.1.0 and PGSharp paid. During setup the message "offset not found. your phone may be incompatible with RAB" came up. |
@gayoso J7 is an old model with physical Navigation button rather than virtual ones, so therefore there is no option for you to hide. All of your problem are quite frankly because the RAB failed to recognize the rightful position of your buttons. |
I see. I noticed there is an option to specify "screen offset" manually. I wanted to try doing this, but I couldn't find an explanation of what that offset means. Do you happen to know? Maybe I can adjust it by trial and error |
Hi! You should make a video showing the initial setup and all the automatic checks RAB does.
I'm using RAB with PGSharp paid with a GPX route. Running the release version on windows.
In my case, RAB gets to a stage where it prints out "RAB will attempt to walk", and then continously presses the "back" button I believe, because the "Do you want to exit Pokemon GO" message keeps appearing and disappearing. No pokemon or pokestops are ever clicked on.
The text was updated successfully, but these errors were encountered: