-
Notifications
You must be signed in to change notification settings - Fork 184
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
ID Verification fails due to the script not detecting Waydroid(?) #83
Comments
Magisk installation has nothing to do with getting google play certification. |
Well, yeah I was confused. The magisk installation script is |
I'm having the same issue! |
Yup, same issue here! |
ERROR: Cannot access gservices.db, make sure gapps is installed and waydroid was started at least once after installation and make sure waydroid is running ! Hi, I realised when I restarted waydroid I no longer had the notification about my device being uncertified. However, testing it again with the sudo python main.py -i I still got the error. magisk installation and every other thing installed without a hitch though. |
There's a PR in draft stage for that includes updates for it. I'll review it and try merging from it as this issue seems to be confusing to users ! |
Yeah, Nonetheless I want to say though many apps still don't function properly, kudos for the development. It is insane technology and I think it will really create a better world. I am new to software development or any developments whatsoever, however I feel the need to say I want to help on this project in any way I can. I strongly believe there are many people out there that will really benefit from it, if not especially me. Lol |
I'm on Arch Linux using Hyprland, after following all the steps to install GApps, I tried to verify the device, however the command wouldn't work, and looking through the issues, I couldn't find out why.
I've run waydroid using both show-full-ui and first-launch and the same error appears.
The workaround from #72 also doesn't seem to work:
The text was updated successfully, but these errors were encountered: