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

Phone VR working so slow #95

Closed
Sanjarbek17 opened this issue Nov 2, 2022 · 7 comments
Closed

Phone VR working so slow #95

Sanjarbek17 opened this issue Nov 2, 2022 · 7 comments

Comments

@Sanjarbek17
Copy link

Hi, PVR Devs, I am facing a crash with the following Error:

java.lang.SecurityException: Permission Denial: starting Intent { act=com.google.vrtoolkit.cardboard.CONFIGURE cmp=com.google.samples.apps.cardboarddemo/com.google.vr.cardboard.paperscope.carton.Settings } from ProcessRecord{a76970 31778:viritualisres.phonevr/u0a521} (pid=31778, uid=10521) not exported from uid 10185

You are doing a good job. Hope this helps ;)

@Sanjarbek17
Copy link
Author

i solved with change qp settings to 10 from 20

@BitBlitObviMormon
Copy link

I solved with change qp settings to 10 from 20

If you solved it can you close the issue?

@Sanjarbek17
Copy link
Author

Sanjarbek17 commented Nov 18, 2022 via email

@BitBlitObviMormon
Copy link

Ok. I'm not a dev, but you'll probably get a faster fix if you post the crash logs and other data listed in the readme. (To be clear, what you submitted is not a log).

@ShootingKing-AM
Copy link
Member

Yes please attach the required logs. I am confused too is it slow or is it a crash or is it two different issues ?

@Sanjarbek17
Copy link
Author

i don't where can i find log it was you was long time age but the problem was it does not crashing but working slow latency to high I guess. I have tried USB cable and wifi I have seen USB cable work well a little bit more than wifi but it is still too slow. i have tried changing configurations. yesterday I have used it and it worked well I guess you guys fix it. alas there is some latency still. you can close this issue

@ShootingKing-AM ShootingKing-AM moved this to To do in Roadmap Apr 10, 2023
@ShootingKing-AM ShootingKing-AM moved this from To do to Work-in-Process Issues in Roadmap Apr 10, 2023
@ShootingKing-AM ShootingKing-AM linked a pull request Apr 10, 2023 that will close this issue
@ShootingKing-AM
Copy link
Member

This has been solved in latest release by using hardware encoding provided by ALVR Server. If its not feel free to reopen the issue.

@ShootingKing-AM ShootingKing-AM moved this from Work-in-Process Issues to Done in Roadmap Jul 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants