Although the S8 will be getting Google Daydream this summer you can still enable the functionality by following the instructions below. It would be nice if developers could include the tweak in there ROM's to save time.
Locate /system/etc/permissions/handheld_core_hardware.xml in your system, and select Edit.
Locate Root Permissions and add <feature name="android.software.vr.mode" /> <feature name="android.hardware.vr.high_performance" /> to the tag.
Reboot your phone.
Launch Daydream and place your phone inside the headset.
Source: VRHeads
I don't find the root permission tag. after set it under permission it work fine. thx for this tutorial.
does anybody knows how can I connect a gear vr controller to daydream?
Has anybody confirmed this working? Do you need the Daydream or can it be used with the gear VR headset and controller?
Related
I was having heavy battery drain from Google Play Services so I searched around and found nothing that would solve my problem. But then I saw the light in the end of the tunnel and it wasn't a train.
The problem was that the Google Play Services couldn't be optimized, generating massive wake locks. So all I had to do is allow it to be optimized editing a single file.
What you'll need: a root file manager (I use Root Browser)
Go to /system/etc/sysconfig, find the file google.xml and edit it
Find the following lines:
Code:
<!-- GmsCore must always have network access for GCM and other things. -->
<allow-in-power-save package="com.google.android.gms" />
Comment the second line so both will look like this:
Code:
<!-- GmsCore must always have network access for GCM and other things. -->
<!-- <allow-in-power-save package="com.google.android.gms" /> -->
Reboot your phone and see if Google Play Services can be optimized now (or is already optimized) in Settings>Battery>3 dot menu>Battery Optimization.
You can confirm after some use that under the Google Play Services battery details the Keep Awake and the Computed Power Use will be much less than before.
It worked on my I9505 running latest JDCTeam's AOSP 6.0.1 with OpenGapps AROMA package.
Didn't had any crashes, delayed WhatsApp messages or any other issue 'til now (almost 2 days).
Thanks for pointing us this tweak.
My 2 cents : after reading some articles, I would underline also this method could lead to drawback on apps based upon GCM. Better to know it before
Optimizing Play services may cause unforeseen consequences (including Android Device Manager or device tracking apps not functioning appropriately). You are advised to calculate the number of installed apps which depends upon Google Cloud Messaging and would be affected by this move.
Click to expand...
Click to collapse
More reading here
Manfrowar said:
I was having heavy battery drain from Google Play Services so I searched around and found nothing that would solve my problem. But then I saw the light in the end of the tunnel and it wasn't a train.
The problem was that the Google Play Services couldn't be optimized, generating massive wake locks. So all I had to do is allow it to be optimized editing a single file.
What you'll need: a root file manager (I use Root Browser)
Go to /system/etc/sysconfig, find the file google.xml and edit it
Find the following lines:
Comment the second line so both will look like this:
Reboot your phone and see if Google Play Services can be optimized now (or is already optimized) in Settings>Battery>3 dot menu>Battery Optimization.
You can confirm after some use that under the Google Play Services battery details the Keep Awake and the Computed Power Use will be much less than before.
It worked on my I9505 running latest JDCTeam's AOSP 6.0.1 with OpenGapps AROMA package.
Didn't had any crashes, delayed WhatsApp messages or any other issue 'til now (almost 2 days).
Click to expand...
Click to collapse
Can you confirm if this works on Nougat? I tried this teak on RR 7.1.1 to no avail. I even deleted the GMS line but after a reboot, GMS is still whitelisted on doze. Thanks.
Google Play Services Optimization
Google Play Services Optimization /system/etc/sysconfig /google.xml and edit it
<!-- GmsCore must always have network access for GCM and other things. -->
<!-- <allow-in-power-save package="com.google.android.gms" /> -->
<allow-in-data-usage-save<!-- package="com.google.android.gms" />
Reboot phone and see if G.P.Services can be optimized now (or is already optimized) Settings>Battery>3 dot menu>Battery Optimization.
Hello there, so this is a simple guide to get PS4 Remote Play working on Rooted phones.
Requirements:
1. A Phone with unlocked BL
2. Magisk
Steps:
Do not open remote play or any sony apps. If you do. Clear data. It remebers it's root check.
Navigate to Magisk Manager
Head to magisk hide and hide all sony apps, like PS store, messages, and remote pay.
Head to settings of the manager and choose Hide Magisk Manager, Rename it to something else. this is the only way I got the remote play to work.
After this I no longer received the error 800 whatever due to rooted device.
As a side note the ds4 control with magisk model for keylayout xml for ds4 does allow for full bluetooth pairing of ds4 control and works inside remote play. I know this was a issue in the past
If this helps you out remember the thanks button
So I finally spent a few moments trying to find a workaround for using peacock on my rooted Nvidia shield.
On rooted devices, Peacock will pretty much instantly force close.. Even if you're passing safety net and using magisk hide.
To workaround this I simply disabled three activities/permissions in the AndroidManifest.xml:
android:name="disabled_com.peacock.peacocktv.safetynet.SafetyNetErrorActivity"
android:name="disabled_com.peacock.peacocktv.ErrorActivity"
<uses-permission android:name="disabled_android.permission.QUERY_ALL_PACKAGES" />
You'll more than likely need to have signature verification disabled, but I'm not 100% positive on that. Also, to be safe before opening the modified apk below, hide magisk from it.
IF YOU PREVIOUSLY HAD PEACOCK INSTALLED, CLEAR DATA AND UNINSTALL IT BEFORE INSTALLING THIS MODDED APK
APK is attached, just extract the zip and install the apk.. let me know if it works for you too..
Mirror Link:
Peacock.TV.ver.1.6.5-AndroidTV.build.222010605.apk - AnonFiles
anonfiles.com
No luck here, still force close on my 2017 Nvidia Shield. I cant even get an unmodded version to run on a unrooted 2017 running 8.2.3. Been trying off and on for over a year. Did have it up and running on an earlier firmware by installing before root. Stopped working after about 30 days.
It didn't work for me
Followed this guide to disable apk verification (didn't work without it) https://www.andnixsh.com/2020/01/how-to-install-unsigned-apk-root-method.html
After successfully installing, I open the app, see the Peacock logo, and then it force closes
Anyone get Peacock to work on rooted Android?
I say we just give Peacock feedback, I 1 starred their app and submitted to support that this is BS. Believe it or not I have a subscription and can't watch on my rooted Nvidia Shield
I was trying to test that on 2019 shield and it would fail from the start, i wonder what am i doing wrong?
If you need a tester, you can PM me and I can test them and let you know
Thank you @bobpiesz, I got your mod working on the FireTV 2nd gen Cube. I can confirm that all of the following are required:
- Your modded Peacock app
- Disabled signature verification in order to install modded Peacock app
- Magisk app needs to be hidden
- Peacock needs to be added to the Magisk denylist, and Enforce Denylist needs to be enabled.
If you open Peacock before you have done all of these steps, the app will remember that the device is rooted. So in this case you have to clear Peacock data & cache.
I wrote up the steps to disable signature verification here as well as the other steps. Feel free to cannibalize what you want
I modded Peacock v1.6.89 (~June 2022). There is at least one new root check in v1.7+ that will have to be found to get the newer releases working.
I removed one of the main activities from v1.6.89 so that the app now only creates 1 icon. On FireTV at least, only one of the two icons would launch without closing, so I removed it.
ok so i tried to use this on a android 11 android tv box and guess what it doesn't work like is there a version of this that actually works
Hi All I need someone to help if you can simplify or explain it more the process that Dante63 used to transfer the SHM from S22 device to the watch4 as I am not able to complete properly the procedure. I only managed to download SHM on the phone.
Use wear installer 2 to simplify the process
Make sure both devices are on the same WiFi network
Enable wireless debugging on watch
Download both APKs. Phone for phone, watch for watch
Open up wear installer 2 on your phone and input your watch IP address and press done
Press custom APK and select watch APK
Press continue and install
Done
naked123 said:
Use wear installer 2 to simplify the process
Make sure both devices are on the same WiFi network
Enable wireless debugging on watch
Download both APKs. Phone for phone, watch for watch
Open up wear installer 2 on your phone and input your watch IP address and press done
Press custom APK and select watch APK
Press continue and install
Done
Click to expand...
Click to collapse
I tried it on and it's installed but shows error as it says that this phone app isn't for watch!!!
Any solution or do you have any APK that's working on Galaxy s22 phone that can be transferred to the watch4?
Select the watch APK not phone APK
Watch APK is about 12mb
What's the APK to be used?
Where can I download it
[RESTRICTIONS-REMOVED] Samsung Health Monitor - WearOS - 1.1.3.002 - Root, Age, Country & Device Restriction Removed - 23rd May 2023
Hello Everyone, I hope you all are fine... ~~~ WearOS WATCHES ONLY ~~~ ~~~ FEATURES, BUGS & FUTURE WORKS~~~ FEATURES: Works on Samsung Watch4 and Watch5 (as mentioned Samsung WearOS Watches), Multilanguage, no root detection, no country...
forum.xda-developers.com
was bored and was curious if anyone had been able to modify the existing Google VR apps to bypass the incompatibility check. thankfully someone has! so if you still have a Google DayDream VR headset you're in luck.
one oddly positive note is that the display perfectly is calibrated to work perfectly with the DayDream 2.0 viewer. I was concerned as with the larger screen, the S22 Ultra would be way out of calibration but that is not the case.
to note, when pairing your daydream Bluetooth controller, you'll run into an issue where the daydream app does not seem to know when pairing is completed. to address switch off your Bluetooth and after 5-10 seconds switch it back on. then the daydream app will confirm pairing is complete and you'll be good to go!
I saw this post a few days ago and I remembered it and thought about the time I got Daydream on incompatible devices even without root, I used a modified Google VR Services APK to bypass the compatability check and got it working on a Note 9 (why is the Note 9 not even supported in the first place it's literally the same as the S9). Anyway it worked pretty well you will just have to do a bit of sideloading to get some apps & games as the Daydream app can only show things that the Play Store deems "compatible". Just install the modified Google VR Services APK, a Daydream APK, and the Daydream Keyboard APK and just sideload most of your apps.
If you want to get your paid apps, use an app called zBackup, it allows you to backup apps as an APK and include it's OBB. Download zBackup on your old Pixel and on your new Pixel. Then backup your paid apps and their OBBs. Then copy the ZIPs and APKs zBackup backed up and restore them on your new Pixel.
Modified VR Services APK:
Trying to get Daydream working on the MZP without root.
Can some one please help me edit the Daydream related APK's to automatically pass the checks in /system/etc/permissions/handheld_core_hardware.xml for and
forum.xda-developers.com
Daydream App APK: https://www.apkmirror.com/apk/google-inc/daydream-daydream/daydream-daydream-1-23-190812026-release/
Daydream Keyboard APK: (https://apkmirror.com/apk/google-in...eam-keyboard-daydream-1-23-190812016-release/)
Click to expand...
Click to collapse