yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 Edge Questions and Answers] hapibanana:
For some reason an app, Clash Royale, for example, the one I where I encounter this problem commonly, sometimes still plays its music even when I am not using the app itself (using web, facebook, etc.). Does anyone here encounter this? I am running the latest version of stock with no root. Just worried that this might cause unintentional battery drain.

I did root before with the hope of fixing my Wi-fi battery drain problem through debloating. Finding out that debloating does not fix my problem, I went and downgraded my firmware to a lower version using files from sammobile hoping that the latest version was what was causing the problem. That still did not work unfortunately so I decided to just live with it (until I see what happens when I upgrade to Nougat) and go back to the latest firmware using the OTA Update. Pretty sure I did everything the right way but is there some chance that I kind of failed flashing in some way causing this to happen? I don't really remember if this actually happened before I rooted and I am not sure if its just a bug in the current version of the firmware.
[Samsung Galaxy S7 Edge Questions and Answers] blu3angel:
Use greenify bro... It works with unrooted phones too... Use it to hibernate your unused app which sometimes running in the background....
[Google Daydream VR] 4RK4N:
[Solved] [Magisk Module] [Oreo Update] Spoofing "Daydream ready device" on a Nexus 6P

TL;DR Skip to the last paragraph!

Daydream runs pretty nice on my n6p. sucks to sideload all apps also not all apps can be found on google. so i wanted play store to recognize my device as "daydream ready" and let me download all daydream apps. a little googleing later i found 2 reddits explaining what to do and saying "it works" in the comments.

https://www.reddit.com/r/oneplus/co...got_daydream_working_on_a_oneplus33t/dbmy2it/ creating 2 new files in /system/etc/permissions/

https://www.reddit.com/r/Android/comments/5hno6u/got_daydream_to_work_on_my_5x_might_work_on_other/ put the 2 feature tags in handheld_core_hardware.xml

none of those worked. i could start sideloaded daydream apps before this. updating/downloading from play store is my issue.

things i didnt try yet:

- a clean flash of the rom then change the permission files in twrp adb then reboot.

- putting the feature tags in 2 seperate files AND in handheld_core_hardware.xml

- https://android.googlesource.com/pl.../etc/android.hardware.vr.high_performance.xml has the <feature name="android.software.vr.mode" /> and the high performance mode tag in it. didnt try that 2 tags in one file way yet.

anybody got this to work yet? if so pls share :D

EDIT: i made a magisk v10 module changing the build.prop. if anyone wants to do it this way feel free to dl the attached module.zip. just downloaded some previously "incompatible" apps. idk what happens if u install it on a device that is not daydream-compatible. n6p is the dev device so it is compat but not daydream-ready. as every dev i take no responsibility for anything. u flash this at ur own risk. that it requires magisk to be installed and working is self-explainatory. just ignore the "wrong vendor.img" warning that pops up on booting.

UPDATE: magisk module disabling bug fixed since some versions ago.

V1.1 : quick and dirty commented out out manufacuturer line and zipped it again. still v10/11 magisk template but it works. just tested. template didnt change much anyway to v12 i think.

DaydreamBypass.zip : version for oreo by [MENTION=3223146]tazzkiller[/MENTION]
[Google Daydream VR] Varking:
Here you go::

1) Get a build.prop editor out of the play store once you have acquired root access.

2) Locate the following strings of texts and change what is written there to "marlin", without the quotes.

ro.build.product

ro.product.device

ro.product.board

ro.product.name

3) Locate the following strings of texts and change what is written there to "Google", without the quotes.

ro.product.manufacturer

4) Locate the following string of text to "Pixel XL", without the quotes.

ro.product.model

5) Locate the following string of text and change what is written there to "google/marlin/marlin:7.1/NDE63L/3273814:user/release-keys" without the quotes.

ro.build.fingerprint

The last part might not be the proper string of text but I am doing this off of memory. Just look for the text that looks like the above and swap it out. After you do this, reboot your device. You will get an error message or two upon booting up and the first boot may take longer than normal but it works. I've personally done it with my 6P to get proper Daydream store games because I wanted to play Gunjack and ArcSlinger. Your build.prop editor should save the original build.prop as a build.prop.bak. When you are done installing your new games, simply change the new build.prop to build.prop.bak1, and the original back to a build.prop

The only bugs I have noticed with this are that during the first 24 hours after doing this I continually got an overheating message while in daydream even when the device wasn't hot. I don't know if time played a factor or multiple reboots but eventually the message stopped popping up. Let me know if it works for you.
[Google Daydream VR] 4RK4N:
oh so its build.prop not permissions. or do i need those too?

will make me a magisk module for the build.prop mods tomorrow or so. and tell u how it worked out. u dont recommend keeping the changed build.prop?
[Google Daydream VR] Varking:
All I did is unlock my bootloader, root my phone, and edit the build.prop. I would keep both build.props. It makes it so you can easily switch to the Pixel XL settings to download and install new games, and then load the original 6P ones again after you are done. Editing the build.prop like above had Google email me a welcome to the Pixel family email, too lol.

But I have 100% working daydream and store access just by doing what I listed above.
[Google Daydream VR] LazerL0rd:
I'm on a Nexus 5X and I'm on Pixel ROM, but I've heard keeping that build.prop change is fine. It doesn't affect Nexus as our OTAs and Stock apps don't need it. It'll just give you access to the Pixel specific apps
[Google Daydream VR] LeoYL:
My experience on Sony Xperia Z1 says that you need to clear data of Google Play Service and Google Play Store after you modify the XMLs in system. I guess that by doing this, your device will be updated as a "Daydream ready phone" in Google's database.

By the way, Xperia Z1's Daydream doesn't work on AOSP 7.1.1. It crashes. Anyway, after I cleaned the data of those two apps, I can download apps like Daydream, Google VR Service, Daydream Keyboard, etc. from Google Play.
[Google Daydream VR] 4RK4N:
UPDATE:

apparently the build.prop modifications crash google camera (latest purenexus). fc upon opening the app.

also various daydream apps (twilight pioneers, vr karts sprint, etc) report "phone overheating" quite fast and force you to "cool the phone" with a "take it out of the headset and close the app" vr screen.

interstingly disabling the magisk module in magisk manager wasnt enough. build.prop was still set to the pixel xl values. uninstalling my module restored original build.prop.

no "wrong vendor.img" warning, google camera works, i still get "performance reduced. phone overheating." overlay warnings while playing daydream games but no force cool off time.

so i just install the module again once a week to check for updates on daydream apps and then uninstall it again.

anybody figured out how to disable the kinda annoying "overheating" warning while playing? ^^
[Google Daydream VR] LazerL0rd:
About the build.prop, don't change manufacturer. That messes up the camera. Allot.
[Google Daydream VR] itinkerstuff:
I'm really interested in making my Samsung Galaxy S7 Edge "Daydream-compatible". I don't even have a Daydream headset, just the regular Gear VR. I really wish that Google would just make a Youtube VR app for Gear VR--it's the only reason why I'd like to give Daydream a try. If you want me to test anything, please let me know!
[Google Daydream VR] 4RK4N:
since it requires the actual daydream headset to activate daydream mode im afraid i cant help you. besides the youtube vr app is optimized for the daydream controller. making it work with the gear vr headset buttons or the gear vr controller would require some rewriting of the yt vr app.
[Google Daydream VR] inteks:
i tested this magisk modul on my s7 edge. seems to work. but then my NFC doesnt work anymore ?!?! so daydream doesnt work.

are really all prop need to be changed?

what build.prop item can make NFC unfunctional?

btw. this is the error i got in Need for Speed VR (logcat) ->

"failed to initialize async reprojection, unsupported device"
[Google Daydream VR] 4RK4N:
try removing the manufacturer line. maybe nfc still works and u can daydream.

just recived my n6p back from rma (ranfom hardware failure) dunno if module still works with latest magisk.

about nfs vr idk. maybe samsung messed up some graphics function. wait no they call it "optimized" xD find a aosp rom and try it again.
[Google Daydream VR] xiaoluwan:
use magisk prompt incompatible

use magisk daydream prompt： ‘’ incompatible phone ‘’

how to deal with .......

my telephone model is Nexus 6

:confused::confused::confused::confused:
[Google Daydream VR] 4RK4N:
What? give us a little more than a few random words pls. ur post makes like no sense sry to day that.

ALSO: changed the module to NOT alter manufacturer. i still wouldnt recommend having the module always running. just tested it. still can dl all daydream apps while module is active. module disabling works now with magisk yay. new version in first post.
[Google Daydream VR] baratheon16:
How to get past this screen?

Not able to proceed even if I enter my credentials.
[Google Daydream VR] baratheon16:
Will this work for leeco lemax2?
[Google Daydream VR] tboy2000:
Guys don't bother. I got Daydream running on my Moto X Style and virtually all of the 3rd party apps don't work. They either crash on launch or are in full screen 2d mode and not split screen 3d mode. Only the Google made Daydream apps seem to work.
[Google Daydream VR] baratheon16:
How did u skip add payment option?
[Google Daydream VR] 4RK4N:
i never had that screen lol. cant help you sorry. i have a paypal linked with my playstore since ages ago maybe thats why it never asked me.
[Google Daydream VR] tboy2000:
I never got that option. maybe because I have paypal linked to playstore as previous guy said.

Seriously, don't waste your time.
[Google Daydream VR] baratheon16:
Ok
[Google Daydream VR] moocow1452:
Running Nexus 5X, Daydream apps work for me if I run Pixelify AND make the core hardware patch. Any chance we could incorporate the core hardware into Pixelify or it's own modules so that OTA can work?
[Google Daydream VR] 4RK4N:
core hardware patch? gimme an update on this. i never nedded it on my 6p. what does it do? thinking about updating the module once magisk v13 is ready
[Google Daydream VR] moocow1452:
The core hardware patch is the update to the Core Hardware file in /system to let any nougat device have access to Daydream, not just approved or Dev models.

http://9to5google.com/2017/02/01/how-to-enable-daydream-vr-on-any-android-nougat-smartphone/

Found another module that's supposed to bypass it, but I haven't tested it yet.

https://www.androidfilehost.com/?fid=745425885120704654
[Google Daydream VR] 4RK4N:
ah that one you mean. that could be difficult i think. handheld_core_hardware.xml is different for each device and there is no tool like resetprop for injecting lines. replacing the complete handheld_core_hardware.xml will break lots of things too i guess ^^

EDIT: the 2 lines added to handheld_core_hardware.xml shouldnt cause any effect in daily use. unlike the build.prop modifications. so why not leave it in handheld_core_hardware.xml and use the module when needed? ^^
[Google Daydream VR] LazerL0rd:
You can use xmlstarlet to inject lines into any system XML file :P it may need compiling for arm devices though.
[Google Daydream VR] Weib67:
Thanks [MENTION=4152720]4RK4N[/MENTION] for your work.

I'm looking for a solution to make all 3rd party games work on my OP5.

At the moment, I added the two lines in my xml files and got indeed access to Daydream apps in PlayStore.

Still, most of third party apps still start in 2D full screen instead of dual side VR view.

Will your module fix this ? Does it run on Magisk 13.3 ?

Thank you. :)

Edit: I ended up trying, and here's the result:

Apps that started in 2D mod now are in 3D VR sbs. So that's cool. However.. there's major tearing on each screen, along with a lot of gliches (as an unstable overclocking).

To get every thing as normal, I had to dirty flash stock rom.

My resquest would be: is it possible to update the. .zip for Magisk 13.3 ? And to test with other emulated model such as the regular Pixel (since it has the same definition as the OP5).

We are so close to make this perfect ! :)
[Google Daydream VR] baratheon16:
How to get past add payment option...I don't want to give my payment details.
[Google Daydream VR] Weib67:
I don't remerber having this screen, maybe because I already buy apps in the PlayStore. So it's probably not a bug, but an unfortunate "feature".

Anyway, not much people seem to be interested into having a proper VR experience with OP5. Also, turning the phone into Pixel XL has a quite a lot of bad side effects, which I don't recommand at all for a daily driver device.

I'll try to multiboot and see how it goes on different rom and kernel combinaisons. :silly:
[Google Daydream VR] amandh:
Glitchy Screen On OP5

Even i am facing the same problem with my OP5. Both the screen having some art effects. Any suggestions how to solve it. Thanks
[Google Daydream VR] Weib67:
You could try on non OOS based rom, such as LOS or any AOSP rom. Maybe even with some custom kernels.

My plan is to wait for a stable release of dualboot/multiboot patcher (https://xdaforums.com/oneplus-5/development/patcher-dualboot-multiboot-oneplus-5-t3633150), and then install a second rom to test.

"Pixelify" my OP5 gives too many side effects for me to keep it. Nothing extrem, but I want my daily driver rom to be as clean as possible.

Feedbacks are welcome if you try on any AOSP rom. :fingers-crossed:
[Google Daydream VR] TheRussoGm:
I'm waiting to see if a Pixelify 2 could fix the glitches, with the Pixel 2 XL build.prop changes, I think it will work on OP5 that way, both have the same processor.
[Google Daydream VR] dracinn:
I just installed on vanilla 8.0 October security patch Nexus 6P and it doesn't allow me to download Daydream like in the past.
[Google Daydream VR] 4RK4N:
havent done anything to my oreo yet. i wait for purenexus oreo before i start with magisk and co again. currently on stock without anything.

or i have pixel 2 xl next month :D
[Google Daydream VR] etaPlease:
Can we expect pixel 2 device spoofing?
[Google Daydream VR] dracinn:
[MENTION=4152720]4RK4N[/MENTION] do you plan on adding this to the Magisk module repo?
[Google Daydream VR] ElMaxYT:
Hello, i have a Moto X Pure Edition with SuperSU, and when i edit build.prop to make the phone be recognized as a pixel, it still says it's a Moto X Pure Edition after rebooting!
[Google Daydream VR] 9rief:
Hi. Not sure that is correct thread though there are not so many threads for daydream. Anyway, thanks for your recipe - it was working on my xiaomi mi5s plus until both daydream and vr services apps hadn't updated a couple of days ago. Version 1.8 was working but both 1.10 crash in native code (somewhere in libvrcore.so). Am I alone with that problem? Is there any cure?

Also, not so many games are working even on 1.8. For example, nfc, keep talking, gunship battle and layers of fear work fine while a lot of others show fullscreen picture which remains interactive for controller but not responding to gyroscope. Is it a known issue and is related to daydream/incompatible model or something with my own phone is wrong?

Any help, advice or something would be greatly appreciated.
[Google Daydream VR] bigb159:
I have installed the Magisk module and rebooted my XZ Premium and am now able to install Daydream apps. I'll report back any issues if I find them.
[Google Daydream VR] :
Having problems here. Installed the module, rebooted but still playstore detects nexus 6p as not daydream ready. Furthermore, this also happens when launching the sideloaded daydream app.

Weird thing is, this still fools any other apps checking for your phone model (ex rootchecker detects as pixelXL)

Got a Nexus 6p magisk rooted (v14) on stock android oreo 8.0.0

Anyone with the same problem?
[Google Daydream VR] dalstam:
Same problem here. OP5T with oreo update. Nougat worked like a charm. I think it is oreo related issue

---------- Post added at 11:42 PM ---------- Previous post was at 11:42 PM ----------

Same problem here. OP5T with oreo update. Nougat worked like a charm. I think it is oreo related issue
[Google Daydream VR] tazzkiller:
if you want i have created an updated module for oreo that works for me on the oneplus3.

You just have to deactivate it in the daydream developer options "motion latency" to remove the black bar
[Google Daydream VR] 4RK4N:
thx. featured and credited in OP so ppl find it better.

there is no recovery yet for my new phone so no magisk. once i have that again i try to get daydream running. kirin 659 should have enough power.
[Google Daydream VR] numios:
hi! i tried to install the both modules on my XZP G8142. The first module was not installed, but the 2nd was instaled and Magisk v16 showed DONE. how to install the first module Pixelfly and enable Daydream VR support?
[Google Daydream VR] 4RK4N:
the second one should alrdy do that. its the same as my old module but updated for oreo
[Google Daydream VR] numios:
thanks a lot! all apps work now with 3D! your module is great!
[Google Daydream VR] MrPhilo:
What line does this file add? Gonna try it on my 5T
[Google Daydream VR] Thempo:
I added the two lines to the hardware file thingy in system/etc/permissions/ and I added the module DaydreamBypass for oreo. I'm using a Mi A1 phone and everytime I click on the Daydream Launcher button inside the app it closes the app. Same thing happens when I open other Daydream supported VRApps. Any fix for this?
[Google Daydream VR] VAHLTE:
Support on Pie?

Will this be made to work on unsupported Android Pie devices, such as the Essential PH-1 or the OnePlus 6?

I know of the old manual solution, but it doesn't work. Neither does your method
[Google Daydream VR] itsdundee:
Hey guys, everything works fine on xperia xz premium but the screen ratio is like 21:9, but i need 16:9, does anyone know a solution for this?
[OnePlus 3T Questions & Answers] robdam1001:
Was this part of the Nougat upgrade?
[OnePlus 3T Questions & Answers] the_rooter:
Lte if available through your carrier has always been there, but Im guessing ur talking about the little lte next to ur signal bars.
[OnePlus 3T Questions & Answers] robdam1001:
Yes, sorry, the LTE icon is now showing. Was that part of the Nougat upgrade?
[OnePlus 3T Questions & Answers] worldsoutro:
It was :)
[OnePlus 3T Questions & Answers] the_rooter:
Lte symbol yes but I do notice the + sign still shows every now and then the lte symbol
[OnePlus 3T Questions & Answers] worldsoutro:
that's just informing you of carrier aggravation
[G3 General] Faheem anjum:
Problem : Mcafee lock

you cant Access to Download mod You Cant Access To phone Menu You Can Flash it !!!

https://dl.xda-developers.com/2/8/2....jpg?key=YPc5EA4gmgRbQo4KVOpFBw&ts=1484028957

Since There is no other way to bypass it only can be remove via Tp method

boardiag download from here

G3 Tp pic Download From here

G3 Tot Files Download From here

drivers download from here

If it is Save your time Feel Free Donation : phonesmaster@gmail.com payapl :good::good:

Note : Plz Keep diconnect battery From phone All work will be Done without Battery connect ( mistake will Kill Phone emmc ) So be Careful

[IMG="http://i.imgur.com/H6hGets.png"]http://i.imgur.com/H6hGets.png[/IMG]

@2nd Step

[IMG="http://i.imgur.com/XkDLD7S.png"]http://i.imgur.com/XkDLD7S.png[/IMG]

How to Flash Lg phones Manual Here :https://xdaforums.com/showthread.php?t=2785089
[G3 General] dwcasey:
Excellent work in documenting. Thanks for sharing with the community.
[G3 General] longlife742:
good work...thanks bro

Br,

HassanMalik
[G3 General] stan7734:
Thanks for the reply. I'll be trying that soon as I fix my sm902l. I have a beef with straight talk and I will own the phone or brick it
[G3 General] 12manytimes:
LG D850 Keeps failing when flashing boot partition ? any ideas?
[G3 General] fk5122003:
Watch This

https://www.youtube.com/watch?v=04AgASAWJu8
[XDA Assist] ALI EHTISHAM BUKHARI:
After a day of the downgrade, when i started fifa 16, phone turned of after a while and thenthis appeared on the screen
[General Questions and Answers] SyCoREAPER:
I know I did an internal storage backup with TWRP. I have extracted the system and data TWRP files and see all the apps, system, etc.. but am not seeing the Internal Storage. Can someone please point me to where in the directory structure the internal is? (there is no storage folder or mnt)
[General Questions and Answers] DowntownRDB:
[MENTION=1506211]SyCoREAPER[/MENTION] I'm not sure you can backup internal storage with TWRP. If memory serves me right you can back up System, Cache, Data, Boot and EFS. However, having just woke up maybe I'm not reading your provided information right or possibly I'm completely wrong. When I back up internal storage I use my laptop or PC OS file manager.
[General Questions and Answers] SyCoREAPER:
You know you are right. I remembered seeing it in Wipe, not in Backup. Well that sucks turds. Google Photos backup turned on from now on. At least I have a partial outdated backup but all my TSO (Trans Syberian Orchestra) shots are gone. Had great seats too :mad:
[Xperia Z3 Q&A, Help & Troubleshooting] jaeqer:
Hi guys, recently I changed the screen of my Z3 but now im having sound issues, it doesnt sound as high quality as before and its like there is a scratch sound like when you listen a low quality song.. Can the new screen cause this and is there any fix ?
[P3600 General] ronski:
I have a new job, and with that comes a new phone (KPN), but: no data traffic! (company policy)

I do own a private number (Tmob) which I can update to a data-plan. And to make use of them, I could use a sim-switch, but then I have to switch each time I want to use internet or make a call. But I don't wanna switch! I want 1 sim for voice and 1 for data at the same time, is this impossible??! ;)

probably

But then: as an alternative I could ask KPN for an data only contract as an addon to the contract of my work sim which will be billed by myself. Does anyone have some experience with this? (calling KPN is not possible during the weekend, and I'm very curios)

thanks!
[P3600 General] adejager1:
dual sim

Hello,

I tried a dual sim solution in my trinity, but without success. I bought the latest generation because the older ones can't deal with digital sim's capable of umts. This was a 16th generation dual sim. It worked fine in a verry old nokia but not in my trinity. Tried it in WM5 and WM6 but keeps reporting a sim error.