FORUMS

Daydream unlocker + NFC workaround + controller [Magisk]

37 posts
Thanks Meter: 34
 
By einholzstuhl, Member on 2nd April 2019, 05:35 PM
Post Reply Email Thread
Daydream unlocker logo

Description
Most smartphones on the market do not have Daydream compatability. This locks them out of the usage of all Daydream virtual reality content and the use of the Daydream headset. To change that this thread provides you with the following:

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


Contents
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


Requirements
1. Controller from a Daydream headset

2. Magisk rooted device
Magisk

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

4. Daydream Keyboard
Daydream Keyboard

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

Android 10 Beta
Daydream unlocker


Installation
BEWARE! Setup Instructions have to be done in that exact order!

1. Install Daydream and Daydream Keyboard

2. Open Daydream
->follow the setup instructions

If you get a black screen, hear sounds, see a flat image.
-> Close daydream
-> Open daydream again

3. Enter VR mode
-> Continue until you see "Daydream is not compatible with youre phone"

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

5. Reboot

6. If youre phone does NOT have NFC ×
-> proceed to variant 1.

If youre phone DOES have NFC √
-> proceed to variant 2.






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

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

3. Enjoy




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

2. Enjoy





Troubleshooting

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

2. Open Play Store
-> Delete Google VR Services (Can be done with Titanium Backup too)

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

4. Reboot

5. If youre phone does NOT have NFC
-> proceed to Variant 1.

If youre phone DOES have NFC
-> proceed to Variant 2.






In General
1. Bluetooth has to be enabled for the Daydream controller to work

2. If you open a Daydream app you 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 can 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
1. Drift issue (the screen turns slowly to the left when in vr mode)
-> Place the VR glasses with the phone inside on a flat surface for 10-30 seconds (recalibrates itselve).


2. If you did something wrong when trying to follow the install process
-> Follow the instructions of "How to reset the installation"


3. After some usage of Daydream apps suddenly 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 work anymore (OnePlus apps for example)
Reported by @bschmidy10
Fixes by @jigs4wkiller
-> 1. Only activate Daydream unlocker if you want to use it
-> 2. Or edit the OnePlus apps and remove device check from them


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


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


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


8. The Daydream app might crash if open a VR app inside 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 it might work (or it will just be Carboard mode instead)


9. After activating the module and restarting phone is lagging/freezing, getting past it hungs up or reboots the phone randomly, trebuchted crashes
Reported by @pflatlyne - Nexus 6 - Lineage OS
-> No fix found yet


10. Setup tells you to install VR keyboard but when trying says "Device is incompatible", any other Daydream apps are also shown as incompatible
Reported by @simon_6162 -OnePlus 7 - OxygenOS
Fixes by @simon_6162 - OnePlus 7 - OxygenOS
-> Open Settings
-> Apps & notifications
-> Daydream
-> Force stop/close it
-> Open storage, clear storage, clear cache


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


12. Unity Instand preview app crashed if the module is enabled, works without it but loses support for Daydream apps
Reported by @CombineCrab -OnePlus 7 pro
-> No fix found yet


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


14. After activating Daydream unlocker vibration is disabled entirely
Reported by @grandomegabosses - LG V40 - Android 9
-> No fix found yet

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

Boot TWRP
-> Mount system
-> Go 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...


Credits
Old thread
Old thread by @jigs4wkiller


Thread design
Inspiration
Cosmic-OS
Magisk
Syberia

Daydream logo by @jigs4wkiller

Our team
@einholzstuhl as a community and thread manager/editor
einholzstuhl profile picture
@jigs4wkiller for more technical questions
jigs4wkiller profile picture



Code
@jigs4wkiller, [email protected]



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




Thank you all for your support!
The Following 5 Users Say Thank You to einholzstuhl For This Useful Post: [ View ] Gift einholzstuhl Ad-Free
2nd April 2019, 06:39 PM |#2  
jigs4wkiller's Avatar
Senior Member
Flag Stuttgart
Thanks Meter: 988
 
Donate to Me
More
Thanks for the takeover
2nd April 2019, 06:42 PM |#3  
einholzstuhl's Avatar
OP Member
Thanks Meter: 34
 
More
Quote:
Originally Posted by jigs4wkiller

Thanks for the takeover

Oh my god,
such high prais from the gcam god himselve!
I'am fainting
The Following 2 Users Say Thank You to einholzstuhl For This Useful Post: [ View ] Gift einholzstuhl Ad-Free
10th May 2019, 02:20 PM |#4  
einholzstuhl's Avatar
OP Member
Thanks Meter: 34
 
More
UPDATE! 15.10.2019
-> Daydream unlocker Beta for Android 10 released
-> Quick fix for bootloop on Android 10 addet to bug list

UPDATE! 08.10.2019
A couple people addet to the feedback list.
Daydream unlocker marked as only Android 9 and below compatible currently

UPDATE! 16.09.2019
XDA randomly adds [URL] brackets to my linked pictures which causes it to break them. Fixed for the 10th time.

UPDATE! 24.08.2019
1. ,,Installation" instructions rewritten, Daydream Keyboard should be installed at the beginning. Prevents compatibility problems with NFC devices while setting up Daydream.

UPDATE! 11.08.2019
1. New Daydream logo by jigs4wkiller
2. Some headline names replaced
3. Headlines replaced with pictures
4. Link name shortened
5. Thread design inspiration + new logo addet to credits


UPDATE! 10.08.2019
1. Daydream Enabler from [email protected] Magisk module outdated
-> removed from thread

2. New additions
-> Description
-> Contents
-> Instructions restructured, simplified
-> Bugs + Fixes

Edit:
3. The name of "Daydream enabler" has been changed to "Daydream unlocker" to avoid confusion with [email protected] module on Github

UPDATE! 04.06.2019
A couple more screen resolutions addet.

UPDATE! 11.05.2019
Some visual tweaking for better contrast.

UPDATE! 10.05.2019
Thread updated for better readability + significantly shortened.

[email protected] Magisk module no longer available from the Magisk repo, just from Github. Removed from thread.

UPDATE! 02.04.2019
This thread will now be continued by me @einholzstuhl

New additions:
1. How to fix if daydream does not work anymore even after reinstalling completly,
troubleshooting,
general fixes

2. Manual has been redone entirely
The Following 2 Users Say Thank You to einholzstuhl For This Useful Post: [ View ] Gift einholzstuhl Ad-Free
1st June 2019, 05:27 PM |#5  
bschmidy10's Avatar
Senior Member
Flag Saint Louis
Thanks Meter: 148
 
More
Thank you so much for this ♥️♥️♥️ works like a charm, but the module changes my device ID to a Google pixel, which causes apps particularly for my OnePlus to not function... Is there a way to fix this?
The Following User Says Thank You to bschmidy10 For This Useful Post: [ View ] Gift bschmidy10 Ad-Free
1st June 2019, 07:31 PM |#6  
einholzstuhl's Avatar
OP Member
Thanks Meter: 34
 
More
Quote:
Originally Posted by bschmidy10

Thank you so much for this ♥️♥️♥️ works like a charm, but the module changes my device ID to a Google pixel, which causes apps particularly for my OnePlus to not function... Is there a way to fix this?

The ID change is pretty much the point 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 One Plus apps to work at the same time.
(At least not with this method.)

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

My suggestion:
Only activate the Daydream module when you want to use Daydream and after use disable it.

Thanks for the feedback!
The Following User Says Thank You to einholzstuhl For This Useful Post: [ View ] Gift einholzstuhl Ad-Free
2nd June 2019, 05:52 AM |#7  
bschmidy10's Avatar
Senior Member
Flag Saint Louis
Thanks Meter: 148
 
More
Quote:
Originally Posted by einholzstuhl

The ID change is pretty much the point 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 One Plus apps to work at the same time.
(At least not with this method.)

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

My suggestion:
Only activate the Daydream module when you want to use Daydream and after use disable it.

Thanks 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 only add/fix the build.prop file and permissions and not touch device ID? Or are they locked together?

I will search for the correct build.prop file to edit to see if I can get it working without the module enabled and reply back again.

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

Thank you 👍🤗

***Update***

After researching, I see what you mean about the device ID change. It seems that certain apps require it and others work with just the vr permissions edit. You definitely have the best solution, would there be any benefit to setting to to pixel 3 xl vs OG pixel? Or not important?

And I do not expect anything , but it would be pretty great if you could make a "lite" version of this module without the device ID change or if you could tell me where to look 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 make the edits myself.

Once again, thank you very much. I can't believe there isn't more of a demand for this!

Still so frustrating Google won't just let qualified devices work properly with daydream
2nd June 2019, 07:38 AM |#8  
einholzstuhl's Avatar
OP Member
Thanks Meter: 34
 
More
Quote:
Originally Posted by bschmidy10

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.

That is because youre Build.prop got overwritten by the update propably.


Quote:
Originally Posted by bschmidy10

Is it possible to have a module only add/fix the build.prop file and permissions and not touch device ID? Or are they locked together?

You can try it the way you think it would work and report back


Quote:
Originally Posted by bschmidy10

Would there be any benefit to setting to to pixel 3 xl vs OG pixel? Or not important?

Well it is Google, they like to have exclusive features for their own devices, but I do not think that is the case for Daydream.

Iam not sure if that is still the case but (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 it)


Quote:
Originally Posted by bschmidy10

And I do not expect anything , but it would be pretty great if you could make a "lite" 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 really be worth the amount of work.
So the lite variant should be done individualy if needet.


Quote:
Originally Posted by bschmidy10

I... or if you could tell me where to look 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 make the edits myself.

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

You might also need to change the System.prop

You can compare the build.prop from the module directly with the one in youre device and make changes accordingly.


Quote:

Once again, thank you very much. I can't believe there isn't more of a demand for this!

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

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

Thank you again for youre feedback, much appreciated!
The Following User Says Thank You to einholzstuhl For This Useful Post: [ View ] Gift einholzstuhl Ad-Free
3rd June 2019, 10:15 PM |#9  
bschmidy10's Avatar
Senior Member
Flag Saint Louis
Thanks Meter: 148
 
More
Quote:
Originally Posted by einholzstuhl

That is because youre Build.prop got overwritten by the update propably.



You can try it the way you think it would work and report back




Well it is Google, they like to have exclusive features for their own devices, but I do not think that is the case for Daydream.

Iam not sure if that is still the case but (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 it)



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 really be worth the amount of work.
So the lite variant should be done individualy if needet.



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

You might also need to change the System.prop

You can compare the build.prop from the module directly with the one in youre device and make changes accordingly.




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

Thank you again for youre feedback, much appreciated!



Thank you 😊
The Following User Says Thank You to bschmidy10 For This Useful Post: [ View ] Gift bschmidy10 Ad-Free
4th June 2019, 09:24 AM |#10  
Member
Thanks Meter: 30
 
More
First of all, thanks a lot for the module.

I had some distortions in VR on my OnePlus 7 Pro.
So I changed the values in system.prop to "Pixel 3 XL" and "crosshatch" and it got much better. Most likely because of the similar screen ratio.
The Following User Says Thank You to Kleva94 For This Useful Post: [ View ] Gift Kleva94 Ad-Free
4th June 2019, 12:19 PM |#11  
einholzstuhl's Avatar
OP Member
Thanks Meter: 34
 
More
Quote:
Originally Posted by Kleva94

First of all, thanks a lot for the module.

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

It might be a good idea to release more version for different screen ratios.

Thanks for the input!

Edit:
A couple more screen resolutions addet
The Following User Says Thank You to einholzstuhl For This Useful Post: [ View ] Gift einholzstuhl Ad-Free
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes