I have not flashed the latest LineageOS from Unjustified Dev but I wonder if Daydream is working on it. Did this on my Oneplus One to unlock daydream, wondering if it works on Axon 7. Anyone want to give it a try?
Post from Reddit:
"This requires root, Android 7.0, Google VR Services, and the Daydream app to all be installed on your phone. It also requires a compatible Daydream viewer and controller (I use a Cardboard viewer with the controller emulator running on an old device).
Using a root explorer app, navigate to /system/etc/permissions/handheld_core_hardware.xml. This is where the system features of your phone are listed.
Inside the file is the list of permissions, formatted as XML and nicely commented (as least on my 5X). Add the following lines into the root permissions tag:
<feature name="android.software.vr.mode" /> <feature name="android.hardware.vr.high_performance" />
They might even be mentioned and explained in the comments.
Reboot your device. You should be able to launch Daydream from the app."
feedback on daydream on lineage14.1 zte axon 7
I've been playing with daydream on lineage+zte axon 7, and here's my initial thoughts.
* To get the display working, you need to make the following change: switch under Settings -> Display -> "When device is in VR" , from "Reduce blur (recommended)" to "Reduce flicker" makes the display work.
* not initially, but shortly after using it will prompt to install daydream keyboard and update the firmware on the controller. that worked without issue
* The speakers aren't stereo, and are both playing left channel (unrelated to daydream) so I use headphones.
* The power button has an unfortunate location, and if you don't carefully apply the view strap, you will power off the phone or bring up the shutdown menu. after a while, you get used to that.
* the phone will get hot after a while.
* There seems to be some recurring motion tracking lag, and the controller seems lose connection from time to time.
Most of the experience is on par with a stock moto z daydream experience.
mhodges85 said:
I have not flashed the latest LineageOS from Unjustified Dev but I wonder if Daydream is working on it. Did this on my Oneplus One to unlock daydream, wondering if it works on Axon 7. Anyone want to give it a try?
Post from Reddit:
"This requires root, Android 7.0, Google VR Services, and the Daydream app to all be installed on your phone. It also requires a compatible Daydream viewer and controller (I use a Cardboard viewer with the controller emulator running on an old device).
Using a root explorer app, navigate to /system/etc/permissions/handheld_core_hardware.xml. This is where the system features of your phone are listed.
Inside the file is the list of permissions, formatted as XML and nicely commented (as least on my 5X). Add the following lines into the root permissions tag:
<feature name="android.software.vr.mode" /> <feature name="android.hardware.vr.high_performance" />
They might even be mentioned and explained in the comments.
Reboot your device. You should be able to launch Daydream from the app."
Click to expand...
Click to collapse
It works just fine with 14.1. I didn't have to change anything
Hi,
i recently installed Lineage nightly from 20.02.17 and tryed out the Daydream Headset. The standard apps including Youtube, Pictures and PlayStore are working very well. But some VR apps i've tested (eg. Poly Runner, Horizons) are not shown in VR mode. I've installed and start the apps out of Daydream an they are shown full screen and not splitted in two Displays for the Headset.
Has anyone else the same problem or any ideas how to solve this?
Thanks in advance
I can't install Daydream Keyboard.....incompatible app in playstore....any ideias?
Related
I had high hopes (very high!) that I could get tasker to run on the ouya, unfortunately I have not had any luck as of yet.
Maps was installed, as was a few files that needed to be manually installed in /system, but unfortunately neither seemed to work.
Has anybody had any luck? Please let me know if you did, I had big plans for this little system and tasker was a key piece to it.
Thanks.
Well, apparently I'm batting 1000 tonight on threads.
A reboot allowed instillation of the tasker trial version.
It looks like everything works, or as much as you would expect for the ouya. I did two test tasks. First was just a screen popup, which obviously worked great. The other was a reboot to test root access, and this also worked perfect (say hello to automated weekly reboots!).
Now, to see if autoremote can be made to work, and then on to autovoice or utter! and the inherently difficult prospect that will be.
Snoman002 said:
Well, apparently I'm batting 1000 tonight on threads.
A reboot allowed instillation of the tasker trial version.
It looks like everything works, or as much as you would expect for the ouya. I did two test tasks. First was just a screen popup, which obviously worked great. The other was a reboot to test root access, and this also worked perfect (say hello to automated weekly reboots!).
Now, to see if autoremote can be made to work, and then on to autovoice or utter! and the inherently difficult prospect that will be.
Click to expand...
Click to collapse
Please periodically update this thread with your progress? Curious to follow suit, though don't have the time to help in the investigations
A few issues with tasker itself, such as I can't download from Google play, it won't recognize my original order #, i can't find 'my' .apk, basically can't get my purchased version working and am stuck on the 7 day trial version. As for functionality it works great.
Current main task is to start XBMC if Autoremote received a certain message, as well as sending a message when xbmc is open and a different one when it closes.
On my tablet when I fire up the Yatse app, Tasker checks to see if XBMC is running, if not it displays a popup asking if I want to start xbmc. If I say yes it sends a command through autoremote which is what triggers tasker to start xbmc.
OK, a few things I have found.
Originally I could not download Tasker through the Play Store as the Ouya showed up as 'incompatible', however after a Play Store crash that removed it from my system, and subsequent reinstall, I can now download it from Google Play. I don't know why this was, but when I first did the play store mod I didn't have busybox installed, I did for the reinstall. I don't need the play version however as I was able to get the 'Trial' version validated, which is good as the direct download has added functionality (that I will never use). To validate the trial version you need to find the 15 digit order number (not the 16 digit Google provides in the email). This is best accomplished by using the 'Contact Crafty Apps' link in the email, and then finding Tasker, the 15 digit order number should then be visible. This only works if you bought Tasker before March 2013 though, otherwise you will need the Play store version (thanks Google :/)
To get Tasker to run you need to be Rooted and move two Google files to the proper location on the Ouya. Tasker will not run without the Google maps framework and oddly enough installing Google maps doesn't install the full framework. You can get these files by flashing the gapps package with CWM, or just install the two files themselves. To get the files unzip the gapps package, I think in the 'framework' folder. You need to move com.Google.android.maps.XML to /system/etc/permissions, and move com.Google.android.maps.jar to /system/framework. This WILL require you to remount /system as writeable. ES File Explorer worked for me (download an old version, 3.0.4 maybe, as the newest Play store version crashes), it was the only free root access file manager to work for me. Remount /system back to the way it was. BTW, I did all of this without adb, it was all done on the system itself with some help from dropbox (unzipped on my nexus, it was easier).
Tasker itself works great and I currently have it sending messages through autoremote to update variables on my other devices, this triggers a popup that asks if I want to start XBMC when I start my XBMC remote app (only if XBMC isn't running). If I select yes then it sends an Autoremote message that triggers a Tasker profile that starts XBMC. I also have Utter! setup to trigger the 'Start XBMC' Auto remote message on my Nexus
My next two tasks will be for an automatic nightly reboot, and a task that sends the Ouya into sleep mode when I start my alarm clock app on my nexus. I'm still trying to think of good ideas to implement. I hope to get a microphone working to use voice commands directly on the Ouya, and my dream is for an IR blaster to work so the Ouya could turn on my TV with voice commands (old TV)
Snoman002 said:
OK, a few things I have found.
Click to expand...
Click to collapse
Wow! I really commend you for your perseverance and willingness to share your experience and findings...people don't realize how much this helps others.
Scenes Working
Hey Snoman002,
I have my Ouya rooted and found a Tasker that can be used to mount and unmount NFS mounts. I have the two google maps files installed and have version 4.2 of Tasker installed. When i try to open the scene or even create a new one Tasker closes and goes back to the Make Menu. Have you seen a similar thing with the version you have been using ?
Thanks
Techhhead33
Techhead33 said:
Hey Snoman002,
I have my Ouya rooted and found a Tasker that can be used to mount and unmount NFS mounts. I have the two google maps files installed and have version 4.2 of Tasker installed. When i try to open the scene or even create a new one Tasker closes and goes back to the Make Menu. Have you seen a similar thing with the version you have been using ?
Thanks
Techhhead33
Click to expand...
Click to collapse
Sadly, other than getting it running initially I have done nothing more with Tasked on my ouya.
Your trying to make a scene in tasked? Scenes are really only for overlays and custom menus (drastic oversimplification I know). I fail to see the need for the complication of a scene just for mounting and unmounting. Perhaps you could change the tasker task to a simple popup menu (which now that I think about it may be a scene...). Popups worked for me, but that's all I can say about it.
Sorry, I'm not here much anymore as my ouya just runs xbmc now. I will try and check in more often.
Although I still consider GearVR being the superior solution, Google ahs come a long way from Cardboard. At the very least enabling Daydream reduces jittering in cardboard apps and there is some cool exclusive content is available.
Guide:
You need a Nougat rom.
You need to be rooted.
Follow the instructions in this post:
https://www.reddit.com/r/Android/comments/5hno6u/got_daydream_to_work_on_my_5x_might_work_on_other/
Using a root explorer app, navigate to /system/etc/permissions/handheld_core_hardware.xml.
<feature name="android.software.vr.mode" /> is already enabled.
<feature name="android.hardware.vr.high_performance" /> is commented out, change accordingly.
Install Daydream app. http://www.apkmirror.com/apk/google-inc/daydream/
Install Google VR Services. http://www.apkmirror.com/apk/google-inc/google-vr-services/
Install Daydream Keyboard. http://www.apkmirror.com/apk/google-inc/daydream-keyboard/
Reboot. If Daydream app was already installed before editing handheld_core_hardware.xml. you need to clear app data and cache of Daydream and Google VR services.
Enable NFC. Charge the Daydream Controller.
Run Daydream app and follow first time instructions. If Games are availalbe inside Daydream you did everything right.
Things working:
All media consumption apps.
Most games including Gunjack 2, Underworld overlord.
Not working:
Need for Speed Unlimited VR. crashes with black screen.
Issues.
Heavy sideward drifting. May be caused by a controller issue.
Occasional flickering.
Double vision especially in Gunjack. In this case use a headset with lens distance adjustment.
Please share your experiences.
Only two issues with this guide for me.
1. No root
2. No Nougat
Sent from my SM-G930F using Tapatalk
Cardboard is just a poor plebs gear vr. I think its actually made for emerging markets
I am talking about Daydream which offers a similar experience to Gear VR and a Wiimote-like remote controller .
i bought a daydram view.
i bought need for speed no limits vr. (50% sale i'm a big fan of this series)
i followed this guide -> https://forums.oneplus.net/threads/...ream-vr-fully-running-on-op3-oxygenos.479505/
i also tryed to set this ->ro.product.device=sailfish
and this -> https://forum.xda-developers.com/mo.../spoofing-daydream-compatible-device-t3534943
no luck
this is the error i got in Need for Speed VR (logcat) ->
"failed to initialize async reprojection, unsupported device"
i hope someone get it to run!!!
btw. this also does not work https://play.google.com/store/apps/details?id=com.wb.fantasticbeasts.vr
Doesn't work for my either. Done all the above. Tried pixelify, sailfish etc etc.
Either I just get a black screen with white vertical separator and sound but no video
Or
I get the game running but in 2D mode and not split screen.
I have spent way too much of my time trying to get it to work. I wonder if it only works on Snapdragon variant of S7 Edge as I have the Exynos version.
Once I got YouTube VR to briefly work where I could see an image duplicated split screen but it was not moving. Almost as if there was no gyro sensor.
I really hope someone can put me out of my grief with a solution.
Does it work with Oreo?
Will the following apps work
- Netflix VR
- Youtube VR
- Keep talking and nobody explodes
Thanks
Dacoco said:
Does it work with Oreo?
Will the following apps work
- Netflix VR
- Youtube VR
- Keep talking and nobody explodes
Thanks
Click to expand...
Click to collapse
At least Netflix and Youtube VR works (downloaded from apkmirror). But the S7 is heavily drifting.
I've been trying for hours now to do the simplest thing. I need some way to make a shortcut to these apps that is its own standalone APK. Here's why:
The long version: I have a Logitech Harmony Hub. It won't launch apps on the Nexus Player directly, but I have a workaround that involves installing Multilanguage Keymap Redefiner on the Nexus Player, and sending a keyboard command that I've mapped to trigger a specific app. For example, sending F1 launches Netflix. This works flawlessly for just about every app, but the exceptions are Google's own apps (Google Play Music and Google Play Movies). When I map a key to launch one of these two apps, nothing happens.
The short version: My Harmony Hub won't launch them directly.
Here's what I've tried so far:
Attempt: Creating an app with Tasker on my phone that launches the app in question. Basically cloning the app.
Result: This works on my phone to launch it, but once I install the app on the Nexus Player, it does nothing. Perhaps the Android TV version of the app is different from the phone version in such a way that it won't allow this to work.
Attempt: Installing Tasker on the Nexus Player so I could attempt the same steps as above, but from the Nexus Player
Result: Can't install Tasker - no way to accept the disclaimer on Android TV because it's not visible (accessibility settings don't help)
Attempt: Backing up Tasker on my phone using Helium, then installing Helium to restore a backup of Tasker that has already accepted the disclaimer.
Result: Tasker won't back up with Helium. It just creates an empty .json file. Everything else seems to back up fine, of course...
Attempt: Installing TV App Repo, and creating a shortcut to the apps in question
Result: unable to create the shortcuts because the apps in question are not downloaded, but are rather preinstalled.
Attempt: used this website: http://atvlauncher.trekgonewild.de/ to try to create an APK from the respective packages.
Result: According to the "apps" section of the Nexus Player settings, the package name for Google Play Music should be com.google.android.music, however, this did not work. Neither did com.google.music, com.android.music, or come.google.android.music.tv. When I say "didn't work," what I mean is that in each case, it said the package was not found. I thought this was odd since I used the same package name as what was shown in the Nexus Player's settings on the first try. If anyone knows the correct package names for these two apps, that may be the solution to the problem.
"Shortcut" apps won't work, because Multilanguage Keymap Redefiner will let you map commands to launch apps, but not shortcuts. Needs to be a standalone app. If anyone knows any other method besides the one I've proposed that will launch the apps in question with a single key press, I'd love to hear it. I know this is an obscure request, but it seems so simple and I'm really frustrated at this point. Not the type to give up at something like this, there's got to be a way, but I can't find it. As a side not, my Nexus Player is not rooted, and I'd really prefer not to go that route if there is any other option. Thanks in advance.
:crying: :crying: :crying:
One of my projects is trying to get Daydreams to work. So far I haven't been able to. I have spent months upon months researching this and have come to several conclusions, however none of them have helped me in activating this feature.
1. Amazon tablets, (Fire 7, HD 8 and 10) have a feature called 'Daydream'. Its a simple screensaver that displays when you are plugged into a PC or charging. There are colors that display or slideshows of on device photos.
2. This feature is stock Android. Nearly every device has the feature enabled, except Amazon tablets.
3. the feature exists, in full, and is blocked out by Amazon.
I have tried several ways to bring the feature out. One being, taking the BasicDreams APK, from another Android device running Lollipop 5.1.1. Basic Dreams should be the catalyst to start the program, but it does not. I have tried it from other android versions too. No matter what, the APK won't brinng out the screensaver.
I have used activity launcher, with no luck. I have used Tasker and a Secure Settings plugin to bring it out. Nope not there either. But tasker does allow me to select the type of daydream I want, it just never launches it.
I have determined there is at least one thing, one word that stops dreams. Its loacted in /system/framework/framework-res.apk. I use a simple app (APK Editor Pro) thhat decompiles the APK. I then tap on files, res, values, bools. In that list is a configuration, 'config_dreamsSupported' which is marked as 'false'. Everything else from then on is in place. I change false to true and the APK will not recompile without errors. It seems Amazon assigns their own daydreams to certain attributes, but then blocks you out from seeing them.
So it seems I am only having trouble compiling a proper APK for the system. If you want to see the settings for daydream, Activity Launcher > all activities > settings > Daydream. Framework: Framework-res.apk > res > values > bools.
I will not rest until I am able to get this working. Any help would be greatly appreciated.
I managed to hunt down a settings.apk of an android 5.1.1 ROM. So as daring as I am, I uninstalled the settings.apk and reinstalled it with the new one I found. The daydream settings menu opens, I can select dreams like Colors. But again, the screensaver doesn't start. I also managed to install a settings.apk from a 4.0 ROM. In doing that, I managed to bring up the actual stock accounts menu. I was able to select all items to sync, remove the misc amazon accounts too. Though there was no daydream settings, most all the other options worked. I might add I was doing
Code:
adb install -r -d com.package.name
after uninstalling the settings.apk and was able to then install any settings.apk from any SDK. If I can rewrite any one of these APKs, we could have stock settings.
However, I don't have screen shots as I had to reboot and I bricked. So I have to sideload back to stock. Though I'm sure the brick was caused by my massive debloating and not from the settings modding.
So I managed to get the say dream settings to launch, but no screensaver yet. However, I have a surprise for later. This will be epic
Sent from my Samsung Galaxy S4 using XDA Labs
After weeks of trying, researching and bricking, I've finally found a way to successfully edit/modify the values of framework-res.apk and SUCCESSFULLY install the modded version. I have enabled the daydream screensaver, however sofar it will only accept the clock as the screensaver. Though I am sure colors won't display because of something I did wrong.
That having been said, you won't believe what else I've been able to activate now
Sent from my Samsung Galaxy S4 using XDA Labs
I've also been trying to do this. I've been unsuccessful. Can I ask how you were able to get it to take?
And my curiosity wants to know what else you've unlocked.
DragonFire1024 said:
After weeks of trying, researching and bricking, I've finally found a way to successfully edit/modify the values of framework-res.apk and SUCCESSFULLY install the modded version. I have enabled the daydream screensaver, however sofar it will only accept the clock as the screensaver. Though I am sure colors won't display because of something I did wrong.
That having been said, you won't believe what else I've been able to activate now
Sent from my Samsung Galaxy S4 using XDA Labs
Click to expand...
Click to collapse
DaRkNesss363 said:
I've also been trying to do this. I've been unsuccessful. Can I ask how you were able to get it to take?
And my curiosity wants to know what else you've unlocked.
Click to expand...
Click to collapse
Here is the day dream activation guide: https://forum.xda-developers.com/hd8-hd10/general/root-enable-daydream-screensaver-change-t3771038
WiFi optimization: https://forum.xda-developers.com/hd8-hd10/general/root-optimize-wifi-t3767868
FireTabletSettings rewritten: https://forum.xda-developers.com/hd...oot-firetabletsettings-apk-rewritten-t3787636
Change lock screen wallpapers WITHOUT Amazon photos: https://forum.xda-developers.com/showpost.php?p=76071092&postcount=2
And more
Sent from my Amazon KFSUWI using XDA Labs
Hello.
i just bought Fire Tablet 7 9th Generation. can any one help me on how to get daydream enabled on it? i really need this enabled. and im not sure if the instructions here will work as they are for older versions of fire tabs.
Hello XDA users, i bought on Amazon warehouse a BOBOVR-z5 with the daydream remote controller, so i wished to try it with my old good phone.
I found this guide: https://www.xda-developers.com/force-daydream-vr-compatibility/
Followed step by step, i had able to start the Daydream app and pairing the controller, but when i tried to start the side by side mode, i got a black screen with stuttered sounds, or in the best scenario a full screen, non-sbs version of the app.
I read that users from other devices, after following the guide, were recognited on play-store as daydream compatible, with all the related apps available for download in the store. This didn't happen to me.
Someone suggest to disable the setup and calibration from the developers menu. Nothing change.
My G2 have: cr droid 3.8 (Nougat 7.1.2) with standard kernel.
Anyone tried to use daydream with our device? Are you able to start the virtual reality experience?