So I have managed to install and download Daydream and Daydream games. When I launch it, either I get the games running in full screen 2D mode (which is useless for VR) or sometimes I get a black screen with the vertical white centre line. Occasionally I hear sound but there is no visual content. Just black screen.
I have tried the sailfish build prop entry.
I have tried pixelify majisk module.
I have of course added the needed 2 lines to etc permissions file.
I have tried a combination of enabling and disabling the above. Nothing works. It's driving me nuts.
I am on latest 7.0 official rom. No custom ROM, just rooted.
What puzzles me I hear so many people getting to to work straight away. Do I need the official Daydream headset? Maybe they don't work as no NFC chip is detected.
I wonder if it only works on phones with Snapdragon and not Exynos?
Anyone succeed?
No one?
Related
Since the last dev preview up to the final release, I've been having some major issues getting Viper4Android to work properly with Spotify and Google Play Music. For whatever reason, it works for a few minutes after the initial Nougat setup, then stops working whenever I'm steaming music. When I look at the driver status, it says "processing: no."
However, on Pocket Casts things are running normally - which is less than ideal since I turn it off when listening to podcasts.
I've forced permissive mode at boot, removed MusicFX, the audio effects file in the root folder, yet I still can't get it to work properly. I've even flashed various "fixes" and versions of Viper4Android, still, nothing changes.
This is exactly what kept me from staying on the dev previews, and I'm bummed to see nothing has changed since the final release.
I'm on the verge of pulling my hair out! Has anyone successfully gotten Viper4Android to work properly on Nougat, and if so, how?
It is entirely possible that viper needs to be updated due to changes in the coding. This would be something you may want to ask about over at the actual viper forum
I'm trying to run NYTVR on my Nexus 4. I also have a Nexus 6, but its too big for the headset. On the N4 when I start the video, all I get is a black screen with sound. Doesn't matter if I'm in VR (split screen) or 360 mode (normal image). On the N6 either work, but of course no headset for the N6.
The Google VR demos do work on the N4, but not NYTVR. Youtube video works on the N4.
One more variable, I'm running Lineage 14.1 on the N4., the N6 is running stock Google 7.1..1.
Any ideas? By necessity I'm runing pico Gapps on the N4 and wonder if thats the issue.
No replies in 10 days.
I would really appreciate it if someone with a stock N4, would give a quick try of the NYTVR app. You don't need a headset. It either shows video or it doesn't, All I get is sound.
My problem could be an N4 limitation, or it could be Lineage. Its really not practical for me to go back to stock just to check.
so for a wile now I've been trying to get gear vr to work with with custom roms, mainly the light weight roms that have removed all Samsung stuff, I've gotten as far as getting most of the needed files installed and being able to launch a vr game, but one thing, once you do launch a game or anything vr and put the headset on you cant mover around on it, when you go to move your head it stays still, and I'm thinking its a driver issue or something not sure , any help to get it working will be awesome, and I'm just wondering why getting gear vr to work on rom is such a grey spot still?
Did you ever figure out how to load the Gear VR on lightweight ROMS? Trying on Project Alice. Not sure what to do. Thanks bud
(non-T-mobile)
I've been experimenting beyond my abilities, it seems. Successfully got Google Daydream to work. Successfully got Google Dialer/Phone to work. Failed at getting Google Camera to work. Now the photos I take with the OnePlus camera app seem to finalize themselves as a perfectly solid green. They also get tagged with EXIF data for a Pixel XL. Force close the moment I try to do video.
I've removed the Google Camera app.
I've gone into the build.prop file and removed the mod for Daydream which lied to say it was a Pixel.
I've restored the build.prop's permissions.
I've cleared OnePlus Camera data.
Rebooted many times.
Installed a generic app store camera. It takes non-green photos, but EXIF still says Pixel XL.
Ideas?
UPDATE... I never figured it out. Ended up going into settings and doing a reset. Even though backup & restore seems to work, it's still a little frustrating. One of the oddest things... in Settings -> About Phone -> Model... it listed "Pixel XL". In the desktop version of Mint, it suggested my paired device was "Marlin" (the codename of the Pixel XL). I hadn't altered anything to be Pixel XL-based. I had put in "sailfish" (the regular sized 1st gen Pixel) into build.prop, but not "marlin". Not sure which thing I poked to cause that mess.
Make sure you back up your things before changing your things!
I just found your thread, trying to fix this issue for myself. Disabled daydream and Google phone magisk modules then rebooted. Problem seems to have been resolved.
I am on the T-Mobile variant, flashed to international.
spudkinks said:
I just found your thread, trying to fix this issue for myself. Disabled daydream and Google phone magisk modules then rebooted. Problem send to have been resolved.
I am on the T-Mobile variant, flashed to international.
Click to expand...
Click to collapse
It's a shame... the Daydream thing seemed to work fairly well, considering the phone's screen resolution. If that's the cause, it's not really worth it for me to loose camera abilities.
I have just got rid of my s9 to get the 6t and now I cant seem to get the galaxy wearable app on my 6t to see my watch.. seeing as they are pretty much exact same chipsets.. is it some in the build.prop I can edit to get it to work?
Not sure about editing the build.prop but I have the Gear Fit 2 Pro and the Gear S3 Frontier both connected to my 6T. I found that sometimes the app is kind of finicky to get connected and I will have to turn Bluetooth off and on again, sometimes a couple of times to get connected the first time. Also keep the screen on your phone on to see if there is a popup to connect. Maybe even cycle the watch off and back on also along with the phone if all else fails. I was ready to give up at one point and it all the sudden connected. If none of that works I'm not sure what else to try but maybe someone else will have some ideas.
tnap1979 said:
I have just got rid of my s9 to get the 6t and now I cant seem to get the galaxy wearable app on my 6t to see my watch.. seeing as they are pretty much exact same chipsets.. is it some in the build.prop I can edit to get it to work?
Click to expand...
Click to collapse
Along with the Galaxy Wearable app there is also a Gear S Plugin that needs to be installed. The first time I set up my Gear S3 Frontier the plugin was automatically installed but when I had to set my watch up a second time I had to manually install the plugin.
alryder said:
Along with the Galaxy Wearable app there is also a Gear S Plugin that needs to be installed. The first time I set up my Gear S3 Frontier the plugin was automatically installed but when I had to set my watch up a second time I had to manually install the plugin.
Click to expand...
Click to collapse
This is good to know...Been a good while since I set mine up so wasn't aware of that. Thanks for the info!
tnap1979 said:
I have just got rid of my s9 to get the 6t and now I cant seem to get the galaxy wearable app on my 6t to see my watch.. seeing as they are pretty much exact same chipsets.. is it some in the build.prop I can edit to get it to work?
Click to expand...
Click to collapse
I have the gear S3 frontier and fit2 pro. I paired them with minimal issues. Did you reset your watch before trying to pair it?
I have an S3 Frontier, and every clean install ROM switch I have to reset the watch. I think they do it for security purposes? Unless someone knows something I don't, I've never found a way to reconnect the watch to a different device without resetting the watch. The backup of the watch puts everything right back once connected, but still kind of annoying (as it adds back in "removed" programs and such).
I have to use the MagiskHide Props Module to get all the correct things installed for my watch to work. However on a stock 6T it should just work. That module should only come into play on a rooted / unlocked device.