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?
Related
Hi you all,
this is probably not the right forum for this request (I don't have a Shield TV, but a Sony 4K TV with built in Android TV).
But I didn't find a better suitable Forum than this one.
I'm new here and generally relatively new with Android. I only got two Android devices at home:
- an Amazon Fire TV in my office and
- a Sony KD 55x8505c 4K Android TV in the living room.
My Smartphones and Tablets all run on iOS - but I realize more and more that it might be helpful to get a small Android Tablet in the near future to benefit from all possibilities Android offers.
Now to my problem:
I wanna use the German Sky Go App on my Android TV. The current version 1.4.3 is installed an it works. However, it's far from perfect because the menus are out of alignments, you can't see episode numbers and if you click anywhere else than the PLAY button, the app crashes.
I had exactly the same issue on the Amazon Fire TV - but there I found a solution. You simply needed to change the display density by typing "am display-density 280" before starting the app and it works perfect. You can automate that by using the app Tasker. So on Fire TV in the office - everything's perfect.
Now I wanted to achieve the same on my Android TV - and therefore I need your help. The command "am display-density 280" doesn't work an the Android TV. I tried entering it directly through a Shell / Terminal. When I started the Tasker App I couldn't get past the Disclaimer. There was no Accept button to be found. In a different forum I found a possible way for tasker by extracting an already activated tasker version from a different Android Device and installing this version on the Android TV. However, I only got the Fire TV as a different device and I have no idea how to extract the app from the Fire TV including the necessary data. But without knowing the right command to actually change the display-density, Tasker wouldn't help me anyway.
So the most important thing is to find a way to change the display-density to 280 first. Afterwards I need to find a way to automate that when the App is launched. Can you please help me?
Greets
z0dac
Hi,
I'm trying to do the same as you. I also read the Fire TV thread and tried Tasker on my Shield TV, which didn't work.
So i guess i'll set up tasker on my phone to change density to 280 when starting SkyGo and back to standard when leaving the app.
Then i have to backup the app+data - either with Helium (no root) or if that fails (which is likely) with Titanium (root, my Shield TV isn't rooted... yet ).
If i succeed, i could share the Tasker backup with you, if you're interested. I'm busy this week, but i might give it a try next week / weekend.
so here´s what i did:
i changed the display density with the adb command "adb shell wm density 280 %% adb reboot"
i could watch a trailer in sky go, but no luck with live streams or movies. so for now no solution from my side
Thank you!
I finally did it!
I installed Android Studio on my Mac including all SDKs. Then I turned Developer Mode on on my Android TV and connected through adb. With your command I was able to switch the display density to 280 and now finally Sky Go looks and works as it should.
However - now the whole Android TV OS is in density 280. I already noticed that the screen keyboard looks a bit odd.
Now the only thing I miss is the possibility to switch the density only for the Sky Go App. On Fire TV I can do that with Tasker, but on Android TV Tasked doesn't work. If anybody could help me with that...?
Thanks again and
Greets
z0dac
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 was just curious if this is something that could be added via root or mods.
Seems like even low end devices are able to cast to Miracast so the missing feature from the Fire tablets seems like a push to get people to buy the Fire TV sticks or whatever.
Would be nice to cast to my projector which has Miracast built in when I am feeling lazy and don't want to power on the PC for proper viewing.
What say you guys?
autobulb said:
I was just curious if this is something that could be added via root or mods.
Seems like even low end devices are able to cast to Miracast so the missing feature from the Fire tablets seems like a push to get people to buy the Fire TV sticks or whatever.
Would be nice to cast to my projector which has Miracast built in when I am feeling lazy and don't want to power on the PC for proper viewing.
What say you guys?
Click to expand...
Click to collapse
I think @DragonFire1024 is working on it too. :laugh:
Here's the deal. I've studied this pretty closely and have a good grasp on how to make this work, at least until it comes to one configuration: wifi_display. It may not seem like much, but it means everything in terms of whether the original miracast works, or doesn't. There are 2 important settings that need to be enabled; config_enableWifiDisplay in framework-res needs to be set to true; FireTabletSettings.apk needs to have wifi_display in set in res/values/public and I have yet to come across a settings APK with that value present.
Solutions: 1) push Java code to the public class of the apk (I don't know enough about Java to do so). The code can be found on the Android Open Source Project website, if you know how to navigate it. 2) direct edit of the smali code of the apk. I have studied a bit of how to do this but still don't grasp the ability. Every decompiler is different and one never says the same from the other. (Yes smali is that difficult).
The best chance is through smali, it's the easiest method imho. Until that can be achieved, the original miracast is lost. I've tried other work arounds including the famous kensuke research on GitHub, and have come up with a brick each time. So you are left with no options really, because we can't use Chromecast on these devices because we're considered uncertified, even when rooted. I'll continue my work on it, but until I can figure it out, you can bring up the UI and watch compatible devices come into and out of range, but I have yet to get any to connect. WiFi P2P works perfectly in terms of connection, but I haven't used it for anything else and still won't connect via cast screen aka miracast.
Sent from my Moto E4 using XDA Labs
Also just a heads up. The HD 8 appears to fully support Miracast, at least in the 2016 device. The build.prop is set up 100% right, MTK actually supports WFD in this device according to the actual ProjectConfig.mk, including both sink and source. I believe the only thing preventing it from working is rooting the device to perform the modification to the framework. If I am not mistaken, that would enable wifi_display in the public.xml because the sink and source are already supported pieces of hardware directly through MTK. Whereas in the HD 10, none of it is supported by MTK. In other words Amazon didn't include support in the build they ordered from MTK for the HD 10. So this requires more jerry rigging unfortunately. If root is ever gotten for the HD 8, it may make this a lot easier.
@DragonFire1024
I am on an hd 10 2017 os version 5610 (retyre xposed and rooted version). I know this is a thread started about miracast but I saw this comment:
So you are left with no options really, because we can't use Chromecast on these devices because we're considered uncertified, even when rooted
I am able to cast to both my chromecast's (one gen one and one gen 2) older non hd ones, without an issue. So far have cast from the discovery go app, science go app, history app, plex and netflix... all downloaded from google playstore (maybe i got netflix from amazon). For some reason HBO Go doesn't show a cast icon so couldn't test that but at least for me chromecast functionality is definitely there and working 100%
Would be happy to test any other apps people might be interested in but sounds like others had no functionality at all not that we had an app compatibility issue.
adm1jtg said:
@DragonFire1024
I am on an hd 10 2017 os version 5610 (retyre xposed and rooted version). I know this is a thread started about miracast but I saw this comment:
So you are left with no options really, because we can't use Chromecast on these devices because we're considered uncertified, even when rooted
I am able to cast to both my chromecast's (one gen one and one gen 2) older non hd ones, without an issue. So far have cast from the discovery go app, science go app, history app, plex and netflix... all downloaded from google playstore (maybe i got netflix from amazon). For some reason HBO Go doesn't show a cast icon so couldn't test that but at least for me chromecast functionality is definitely there and working 100%
Would be happy to test any other apps people might be interested in but sounds like others had no functionality at all not that we had an app compatibility issue.
Click to expand...
Click to collapse
Chromecast might be a fluke. I've not been able to get it to work, but I'm not so much interested in it. The equivalent of the original miracast, remodroid worked on all my tablets, but haven't tried it on my HD 10.
Sent from my Moto E4 using XDA Labs
DragonFire1024 said:
Chromecast might be a fluke. I've not been able to get it to work, but I'm not so much interested in it. The equivalent of the original miracast, remodroid worked on all my tablets, but haven't tried it on my HD 10.
Sent from my Moto E4 using XDA Labs
Click to expand...
Click to collapse
You are correct, I downloaded remodroid onto my hd 10 and it didn't find any devices. My roku in screen mirroring mode (auto allow) I am told should be seen as a miracast device, but the program didn't find any devices, even when I tried to connect directly to the ip address.
adm1jtg said:
You are correct, I downloaded remodroid onto my hd 10 and it didn't find any devices. My roku in screen mirroring mode (auto allow) I am told should be seen as a miracast device, but the program didn't find any devices, even when I tried to connect directly to the ip address.
Click to expand...
Click to collapse
There are a few factors on the HD 10 which ultimately prevent screen mirroring from working. At least what we know as Miracast. I'm going to have to do some more research on how to edit smali code that would allow for the wi-fi display to be active. But Amazon doesn't include it in the public class of their Java code so I have to do it manually and I'm not sure how to do so.
Sent from my Moto E4 using XDA Labs
Want to start some research about this board. I know that JTC uses it in its TV sets, but its probably widely spread among OEM TVs.
To discover firmware I unpacked a update and found a file: CtvUpgrade.bin that starts with a list of partitions that are in its ROM.
Anyone knows more about the format or want to join me here?
Hi.
The board is a cultraview they like to have a custom OS from Zeasn on it.
To be recognized by the launcher cultraview_open_launcher.
This is built into cheap models.
You get to the hidden tv menu through input / source and then 2580.
I myself have a device from kb-elements with cultraview board and custom OS.
Oh, well - good to have a bro here
I could figure our already some thing in the Service Menu (Overscan, Reduce backlight further more).
But sill I just have quite a few questions:
Does your board allow record broadcast?
Could you get rid of the annoying "Energy waste" pop-ups if you increase volume?
Did you get root access to it?
A german bro.
No root is only possible with a root OS version which then has to be flashed Via USB.
This will void the guarantee.
Especially since at least for me it is an OS adapted by Zeasn.
I suspect that JTC is similar to kb-elements.
The file ctvupdate is only firmware for the board.
I would avoid the ctv mode at least when the backlight is deactivated.
Yeah, where are you from? I am not so afraid of guarantie. But I need to know more about. It would be cool to have a real Android, so where all apps will work. Widevine would be cool.
I've seen different update files for same TV with different serial numbers. Guess it is just the different panel. Would be great to separate android from the HW-specific stuff.
Does your TV allows recording?
Lower Saxony.
The cultraview board is often built into cheap devices.
Jtc / Jay tech, TCL, Hisens, KB elements.
Unfortunately, widevine is not on it and the Android is also an adapted "not Google" version.
Playstore ect are installed, if at all, which sometimes leads to problems.
Root access is also not possible. Unless you have an update for the USB stick and modefiert it for root access.
But that is beyond my knowledge.
Yes PVR works, even on a USB stick which sometimes does not work.
If necessary, it could also be activated in the service menu.
For me Playstore isn't working anymore. Although all other apps does have network it complains not to have it.
I manually updated to latest gsf and gms (Service Framework and Playservices for Android 9+) and also to the latest Playstore. I found that I have to install the Playstore for Android TV [8]. Installing the normal one [0] works, but after starting it complains with: This version is not compatible to device.
Nevertheless it keeps non operational with "no network". Help!
I am wondering what can prevent Playstore from working? Is it because of Android TV?
I am pretty sure the Android on this TV is far from perfect, but hey - why no PlayStore. I think once it worked.
Hi all, wondering if anyone has attempted messing with this unit - found nothing on Google/duckduckgo.
Had it 2ish years, been a glitchy little monster and apps like Hulu show incompatibility (though they are 'preloaded' and on the menu). So far as I can tell the system OS has never been updated and am curious what might be done to refresh it?
TheDrake2k said:
Hi all, wondering if anyone has attempted messing with this unit - found nothing on Google/duckduckgo.
Had it 2ish years, been a glitchy little monster and apps like Hulu show incompatibility (though they are 'preloaded' and on the menu). So far as I can tell the system OS has never been updated and am curious what might be done to refresh it?
Click to expand...
Click to collapse
Unfortunately most android TV's don't get updates because the manufacturer doesn't take the time or resources to make an update and push it to the TV's.
As for glitches and apps I would try expanding it's memory using a flash drive and moving apps to it and letting the device use it as internal storage. And I'd use a PC or laptop and download the free program called "adb app control" and use the debloat option and clean some stuff off it. I'd also suggest getting a lighter launcher than the default one. There's a few options here -> Link but I like one called dashboard from the playstore. Also install a launcher manager and/or button mapper (both are free). Hopefully some or all of this helps make your tv a little snappier. I have a fairly new Hisense android tv and I did all this and it feels a lot better than stock.