Can You Use Daydream App With Gear Vr on Pixel UPDATED

Can You Use Daydream App With Gear Vr on Pixel

You are using an out of appointment browser. It may not display this or other websites correctly.
You should upgrade or apply an culling browser.
einholzstuhl
  • #1
ZPmy1Tz.png
CU40QZs.png
Almost smartphones on the market practice non have Daydream compatability. This locks them out of the usage of all Daydream virtual reality content and the use of the Fantasize headset. To modify that this thread provides you with the following:

one. How to enable Daydream compatibility for any phone, with or without NFC
2. Unlocks Pixel sectional apps available in the Play Store

cM1ee9Y.png
Requirements
Installation
______Variant 1. Phones WITHOUT NFC
______Variant 2. Phones WITH NFC
Troubleshooting
______How to reset the installation
______In General
______Bugs + Fixes
Tests
______Devices/systems
______Apps
Credits
______Old thread
______Our team
______Code
______Feedback
IaAAYET.png
1. Controller from a Daydream headset

2. Magisk rooted device
Magisk

3. Daydream app (Non from Play Store! - it will not work!)
Daydream

4. Daydream Keyboard
Daydream Keyboard

5. Daydream unlocker
Android ix or below
(Apply the resolution which is the closest to youre phone.)
Daydream unlocker

Android x Beta
Daydream unlocker

YAdmvMo.png
BEWARE! Setup Instructions accept to be done in that exact lodge!

1. Install Daydream and Daydream Keyboard

2. Open Fantasize
->follow the setup instructions

If you lot go a black screen, hear sounds, see a flat image.
-> Shut fantasize
-> Open daydream again

three. Enter VR mode
-> Continue until you come across "Daydream is non compatible with youre phone"

four. Install Daydream unlocker (one of youre chosen Magisk modules)

five. Reboot

six. If youre phone does Non have NFC ×
-> proceed to variant ane.

If youre phone DOES accept NFC √
-> go along to variant ii.

Variant 1. Phones WITHOUT NFC ×
1. Open Daydream
-> Settings
-> VR Settings
-> Setup everything in Troubleshooting
-> NFC (just ignore information technology), headset (Daydream or Daydream 2017), controller

2. NFC workaround
-> Open VR settings
-> Developer options
-> Enable "Skip VR entry scenes" (otherwise you will e'er be asked to enable NFC)

three. Enjoy

Variant 2. Phones WITH NFC
1. Open up Daydream
-> Enter VR Mode
-> Follow the setup

2. Enjoy

x6qOYVS.png

How to reset the installation
BEWARE! Setup Instructions accept to be done in that exact lodge!
1. Delete Daydream

2. Open Play Store
-> Delete Google VR Services (Tin can be washed with Titanium Backup besides)

3. Deactivate Daydream unlocker (one of youre called Magisk modules)

4. Reboot

5. If youre phone does NOT accept NFC
-> proceed to Variant ane.

If youre telephone DOES accept NFC
-> go along to Variant 2.

In Full general
1. Bluetooth has to exist enabled for the Daydream controller to work

2. If yous open a Daydream app you lot have to switch in the VR settings the headset to Daydream, or you can not use the Daydream controller
-> Daydream app -> Daydream headset
-> Cardboard app -> Cardbord headset

You tin open the VR settings when you open a VR app by touching the white gear symbol and select VR Settings, or in the Daydream app.

Bugs + Fixes
ane. Drift issue (the screen turns slowly to the left when in vr mode)
-> Place the VR glasses with the telephone within on a flat surface for x-30 seconds (recalibrates itselve).

ii. If you did something incorrect when trying to follow the install procedure
-> Follow the instructions of "How to reset the installation"

3. After some usage of Daydream apps all of a sudden Daydream apps wont work anymore or crash
-> Follow the instructions of "How to reset the installation"

4. Device ID change to Google Pixel causes some apps to not piece of work anymore (OnePlus apps for example)
Reported by @bschmidy10
Fixes by @jigs4wkiller
-> i. But actuate Fantasize unlocker if you desire to utilize it
-> 2. Or edit the OnePlus apps and remove device check from them

5. Distortions in VR, stagger/smear on the edges
Reported past @Kleva94, @pbergonzi
Fixes by @Kleva94
-> Attempt a module with a different resolution

6. Subsequently putting the phone in the headset Daydream crashes
Reported past @masoodsuliman - OnePlus 7 pro
-> Follow the instructions of "How to reset the installation"

seven. I installed it twice and it does non work!
Reported past @masoodsuliman - OnePlus 7 pro
-> Follow the instructions of "How to reset the installation"
-> Still does not work? -> Try a different resolution

8. The Fantasize app might crash if open a VR app within of it
Reported by @masoodsuliman - OnePlus 7 pro
Fixes by @masoodsuliman - OnePlus 7 pro
-> If you open a VR app from the app drawer instead information technology might work (or it will just be Carboard mode instead)

9. After activating the module and restarting telephone is lagging/freezing, getting past it hungs upward or reboots the phone randomly, trebuchted crashes
Reported by @pflatlyne - Nexus half dozen - Lineage Os
-> No ready found yet

x. Setup tells you to install VR keyboard just when trying says "Device is incompatible", any other Daydream apps are too shown every bit incompatible
Reported by @simon_6162 -OnePlus 7 - OxygenOS
Fixes by @simon_6162 - OnePlus 7 - OxygenOS
-> Open Settings
-> Apps & notifications
-> Daydream
-> Forcefulness stop/close it
-> Open storage, clear storage, clear enshroud

11. Other VR applications (example iVRy) rotate 90 degrees on some centrality, some directions are inverted
Reported by @CombineCrab - OnePlus vii pro
Fixes by @CombineCrab - OnePlus seven pro
-> Disable the Daydream module
-> Reboot

12. Unity Instand preview app crashed if the module is enabled, works without it but loses back up for Daydream apps
Reported by @CombineCrab -OnePlus 7 pro
-> No gear up constitute nonetheless

13. While activating Fantasize unlocker Magisk says "This is not a module"
Reported by @grandomegabosses - LG V40 - Android ix
-> Update Magisk (If it still does not work report it)

fourteen. After activating Fantasize unlocker vibration is disabled entirely
Reported by @grandomegabosses - LG V40 - Android 9
-> No fix found even so

xv. Daydream unlocker on Android 10 causes bootloop
Reported by @The Jack of Clubs - Android 10
Reported by @adam3914 - OnePlus 7 Pro - Android x
Fixes by @Czarmstrong - Android 10
Fixes by @adam3914 - OnePlus 7 pro - Android x
Fixes past @jigs4wkiller - Xiaomi Mi 8 - Android 10

Kick TWRP
-> Mountain system
-> Get to the file explorer and navigate to "data/adb/modules"
-> Delete the "daydream" folder and reboot

Tests
Devices/systems
Xiaomi Mi A1/Mi 5s/OnePlus 5t, Android 9, Daydream 2017 headset + controller

Apps
Daydream, YoutubeVR, Cardboard,Virtual Virtual Reality,
Fulldive VR, and many more...

ikVPWZl.png
One-time thread
Onetime thread by @jigs4wkiller

Thread pattern
Inspiration
Cosmic-OS
Magisk
Syberia

Daydream logo by @jigs4wkiller

Our team
@einholzstuhl as a community and thread manager/editor

ERaI6wH.png

@jigs4wkiller for more than technical questions
A6r5UVY.png

Lawmaking
@jigs4wkiller, [MENTION=][electronic mail protected][/MENTION]

Feedback
@r0drlgo, @bschmidy10, @Kleva94, @jigs4wkiller, @redpoint73, @pbergonzi, @masoodsuliman, @simon_6162, @CombineCrab, @grandomegabosses, @pflatlyne, @The Jack of Clubs, @adam3914, @Czarmstrong, @Czarmstrong, @Fla010101

:highfive: Thank you all for your support! :highfive:​
Last edited:
jigs4wkiller
  • #2
Thanks for the takeover :highfive:
einholzstuhl
  • #iii
Thanks for the takeover :highfive:
Oh my god,
such high prais from the gcam god himselve!
I'am fainting :crying:
einholzstuhl
  • #4
UPDATE! xv.10.2019
-> Fantasize unlocker Beta for Android 10 released
-> Quick gear up for bootloop on Android 10 addet to bug listing

UPDATE! 08.ten.2019
A couple people addet to the feedback list.
Daydream unlocker marked as merely Android 9 and below uniform currently

UPDATE! xvi.09.2019
XDA randomly adds brackets to my linked pictures wh...es [B]2.[/B] Manual has been redone entirely

Last edited:
bschmidy10
einholzstuhl
  • #vi

The ID change is pretty much the betoken of the module which fakes a device that is Daydream compatible.

So I do not think that it would be possible for Daydream and youre I Plus apps to piece of work at the same time.
(At least not with this method.)

Jigs4wkillers proffer:
It could piece of work if you edit youre Ane Plus apps and remove the device check from them.

My suggestion:
But actuate the Daydream module when you want to use Daydream and subsequently use disable it.

Thanks for the feedback!

bschmidy10
  • #7
The ID modify is pretty much the point of the module which fakes a device that is Daydream uniform.

So I exercise not think that it would be possible for Fantasize and youre Ane Plus apps to work at the same time.
(At least not with this method.)

Jigs4wkillers proposition:
It could work if you edit youre One Plus apps and remove the device check from them.

My proposition:
Only activate the Daydream module when you desire to use Daydream and afterwards use disable it.

Cheers for the feedback!


In the past I have just edited the build.prop to add in the vr bits and it has worked. , The problem was that every rom update would undo my work lol. Is it possible to have a module just add/fix the build.prop file and permissions and non bear on device ID? Or are they locked together?

I volition search for the right build.prop file to edit to encounter if I can get it working without the module enabled and reply back once again.

If not I volition happily follow your advice to enable and disable as needed.

Thanks ??

***Update***

After researching, I see what you lot mean about the device ID modify. It seems that certain apps crave information technology and others work with just the vr permissions edit. You definitely accept the all-time solution, would there be whatsoever do good to setting to to pixel 3 twoscore vs OG pixel? Or not of import?

And I do not expect anything , only it would exist pretty not bad if y'all could brand a "lite" version of this module without the device ID modify or if you could tell me where to expect for how to edit information technology myself. I was unable to find the same "handheld.cadre" build.prop file I used back on my OnePlus 3 (running nougat/Oreo) to alter so I wasn't able to make the edits myself.

One time again, cheers very much. I can't believe there isn't more of a demand for this!

Still then frustrating Google won't just let qualified devices work properly with daydream

einholzstuhl
  • #8
In the past I have just edited the build.prop to add in the vr bits and information technology has worked. , The problem was that every rom update would disengage my work lol.
That is considering youre Build.prop got overwritten by the update propably.
Is it possible to have a module only add/set up the build.prop file and permissions and not touch device ID? Or are they locked together?
You can try information technology the style you call up it would piece of work and report back :)
Would in that location be whatsoever benefit to setting to to pixel 3 xl vs OG pixel? Or not important?

Well it is Google, they similar to accept sectional features for their ain devices, but I exercise non think that is the case for Fantasize.

Iam not certain if that is nonetheless the case only (something similiar was implemented for cardboard which had resolution QR-codes):
Every Smartphone has a certain display size and resulution.
The Google Pixel has about the same size as the MiA1 so I chose that one for the module. (That was the thought behind information technology)

And I practise not expect anything , but information technology would be pretty swell if you could brand a "low-cal" version of this module without the device ID change
The module was intendet to be univerally compatible with any phone. So I would have to make a module for every phone in existence which would not actually exist worth the amount of work.
So the lite variant should be done individualy if needet.
I... or if y'all could tell me where to expect for how to edit it myself. I was unable to find the same "handheld.core" build.prop file I used back on my OnePlus 3 (running nougat/Oreo) to change so I wasn't able to brand the edits myself.
The build.prop is located at:
/system/build.prop

Y'all might besides need to change the System.prop

Y'all can compare the build.prop from the module directly with the ane in youre device and make changes accordingly.

Once more, cheers very much. I tin can't believe there isn't more of a demand for this!

Still and so frustrating Google won't but let qualified devices work properly with fantasize


Daydream is very niche then that is the sorry reality of it. In that location are almost no devices on the market which are Daydream compatible so that will probably not change any time in the future.

Thank you over again for youre feedback, much appreciated!

bschmidy10
  • #nine
That is because youre Build.prop got overwritten by the update propably.

You can try it the way y'all recollect it would work and report back :)

Well it is Google, they like to accept sectional features for their own devices, but I do not remember that is the instance for Daydream.

Iam not certain if that is still the instance but (something similiar was implemented for cardboard which had resolution QR-codes):
Every Smartphone has a certain brandish size and resulution.
The Google Pixel has about the aforementioned size as the MiA1 so I chose that ane for the module. (That was the thought backside information technology)

The module was intendet to exist univerally compatible with any phone. So I would have to make a module for every phone in existence which would not really be worth the amount of work.
And then the light variant should exist done individualy if needet.

The build.prop is located at:
/organisation/build.prop

You might also need to change the System.prop

Y'all can compare the build.prop from the module directly with the one in youre device and make changes appropriately.

Daydream is very niche so that is the distressing reality of information technology. There are nearly no devices on the market which are Daydream uniform and so that will probably not change any time in the future.

Thank you lot once more for youre feedback, much appreciated!

Thanks ?

  • #10
First of all, cheers a lot for the module.

I had some distortions in VR on my OnePlus 7 Pro.
And so I changed the values in organisation.prop to "Pixel 3 Forty" and "crosshatch" and it got much better. Most likely considering of the like screen ratio.

einholzstuhl
  • #11
First of all, cheers a lot for the module.

I had some distortions in VR on my OnePlus 7 Pro.
So I inverse the values in system.prop to "Pixel 3 XL" and "crosshatch" and it got much better. Near likely considering of the like screen ratio.


It might exist a adept idea to release more version for different screen ratios.

Cheers for the input!

Edit:
A couple more screen resolutions addet

redpoint73
Oct 24, 2007
15,259
vi,952
  • #12
Start of all, thanks a lot for the module.

I had some distortions in VR on my OnePlus seven Pro.
So I changed the values in system.prop to "Pixel 3 XL" and "crosshatch" and information technology got much meliorate. Nearly likely because of the similar screen ratio.


How did you become the module working on the OP seven Pro? I downloaded the 2960x1440 version (seemed closest to the telephone'south 3120x 1440 resolution). When flashing in Magisk (nineteen.3), it says "installation failed".

I tried flashing in TWRP (sometimes works for modules that don't install straight from Magisk), but it says "invalid zip format". So maybe not meant to flash in TWRP.

Any info on how you did it would be appreciated.

jigs4wkiller
  • #xiii
How did yous become the module working on the OP vii Pro? I downloaded the 2960x1440 version (seemed closest to the phone's 3120x 1440 resolution). When flashing in Magisk (19.3), information technology says "installation failed".

I tried flashing in TWRP (sometimes works for modules that don't install straight from Magisk), only it says "invalid cypher format". So mayhap not meant to flash in TWRP.

Any info on how you lot did it would be appreciated.

I volition check the module mayhap I made a error

Edit:
Zip reupload, delight download again.

Last edited:
redpoint73
Oct 24, 2007
15,259
6,952
  • #xiv
I will cheque the module maybe I made a mistake

Edit:
Zip reupload, please download once more.


That one worked. Installed the module anyway. Now to attempt the residuum of the steps!

Cheers for your work.

  • #15
Using either the Magisk module download from github or the 2160 x 1080 module from the listing on google drive "This nothing is not a Magisk module."
Last edited:
einholzstuhl
  • #sixteen
Using either the Magisk module download from github or the 2160 x 1080 module from the listing on google drive "This aught is not a Magisk module."

Attempt to update Magisk to the newest version and bank check if Magisk is working correctly.
Last edited:
  • #17
Try to update Magisk to the newest version and bank check if Magisk is working correctly.

Silly me--the google bulldoze re-zips the file to download it--I had to remove it from the initial zippo to become to the folder that held the correct zip.
And the one I had downloaded from github needed to take the files removed from the unzipped folder and zipped.
Thanks for your help, and also wondering if yous tin can make a 2340 x 1080 for the OnePlus 6t? Or if you'll tell me what to edit in one of your zips, I tin can make the edit myself.
jigs4wkiller
  • #18
Silly me--the google bulldoze re-zips the file to download it--I had to remove it from the initial zero to go to the folder that held the correct zilch.
And the one I had downloaded from github needed to take the files removed from the unzipped folder and zipped.
Thanks for your assistance, and too wondering if you tin make a 2340 10 1080 for the OnePlus 6t? Or if y'all'll tell me what to edit in ane of your zips, I can make the edit myself.
Information technology'southward not really necessary to employ the props from a device with the same telephone resolution we only added more device with unlike resolutions because of the user feedback.
  • #nineteen
It's non really necessary to employ the props from a device with the same phone resolution nosotros simply added more device with different resolutions considering of the user feedback.

Cheers.
On testing different iterations of the enabler resolution some behaved erratically--one seemed to stagger a trivial on the edges of things while turning, one seemed to have slightly smeared edges but was more than pixellated.
Notwithstanding, the experience is overall a skillful one, and it sure was squeamish sharing a roller-coaster with Santa!
  • #20
Where is system.prop file? And what is crosshatch setting?

Similar threads

DOWNLOAD HERE

Can You Use Daydream App With Gear Vr on Pixel UPDATED

Posted by: albertgravers1943.blogspot.com

Can You Use Daydream App With Gear Vr on Pixel UPDATED. There are any Can You Use Daydream App With Gear Vr on Pixel UPDATED in here.