Hi there,
did anyone achieve to make Daydream VR work with the OP7T Pro?
I found this tutorial
https://forum.xda-developers.com/mo...oot-required-daydream-android-8-9-10-t4072701
but i wondered if its still possible and a good idea to change the settings mentioned there.
Can i just mount / rw and edit the files mentioned there?
Is it a problem for oneplus updates or something else to "change" the device to a e.g. Pixel 3XL (ro.product.system.device in build.prop)
Thanks
Related
Many programs refuse to download on Google play, giving me the message: This program is not compatible with your device.
I have hunted down the APK files for most of those, and they have all worked flawlessly.
This means that Google play essentially doesn't really work for the Folio 100 IMO.
But maybe if it is possible to change the ID to that of some compatible device like the Motorola Zoom or Asus Transformer things would be better?
Do any of you know how to do that? And which device name or ID is best for getting full market access?
I have installed CyanogenMod 9 Alpha 4, after much tampering, but I can't find the answer to this problem anywhere?
I think you have to edit /system/build.prop file. I'm trying to also do it myself, but there must be a tricky way of doing it, because even with root permissions, I get "read only filesystem" errors and can't modify the file.
Don't know if it applies for this tablet but /system requires a app that can mount it as R/W. On my phone I've used Es File Explorer(free), Solid Explorer(free). There is also root explorer and a few other apps that do the same, all of them require SU. hope it helps
Cheers
anyone knows the lines that need to be edited to make it look like a galaxy tab 10.1??
Hi Guys,
As I have a really opportunity to get me a Nexus 9 32GB + Google dedicated keyboard for a stunning price, I was wondering if it is possible to cast/mirror it's display to a VP be it wired or wireless.
I will root it and I am also almost sure to install a custom ROM to it...
I intend to use it to display my .ppt slides on the University/School VP.
Those usually have a Wi-Fi network, but it's sometimes a real nightmare to get the L/P to connect and, even when I have those, it's sometimes difficult to get a reliable connection to that Wi-Fi network.
Given these considerations, I would like to know if it is possible to cast/mirror the Nexus 9 display to a VP.
It seems that when it came out, the Nexus 9 could not output anything via it's USB port (no SlimPort nor MHL support). Is this still correct or has this been addressed by Google ?
Will I be able to cast/mirror with a Chromecast ? I had the "old" Chromcast but that required to be connected to the internet permanently, so I could not use it... Does the "new" Chromecast allow to cast/mirror directly from the Wi-Fi ?
Will I be able to cast/mirror with Miracast ? It seems that does not require an external netwark as it provides it's own network, but when it was released, it seems the Nexus 9 wasn't compatible with Miracast... There have been some workarounds, but those are for Android LP. Has this been adressed by Google or are the tricks reported here and there also working on Android MM ?
I would really appreciate you answers... and yes, I have done some research, but the results seem to be old (more or less when the N9 was released).
Regards.
NexusPenguin
I think Google doesnt support Miracast tech in their new products. It wants to sell Crapcast to everyone. I read somewhere on xda thats possible to enable Miracast trough root and editing some files.
Found on reddit
If you're rooted, add this to your build.prop. It will re-enable wireless display
persist.debug.wfd.enable=1
Or non root method not confirmed
Grim-Sleeper5d,
You don't even technically need to be rooted. All you need is an unlocked boot loader. You can then use "fastboot boot twrp-2.8.7.2-angler.img" to start TWRP recovery mode.
And from there use "adb shell" to access your device. You can edit either "vi /system/build.prop", or "vi /vendor/build.prop". Make sure you told TWRP to mount these partitions.
Wysłane z mojego GT-I9295 przy użyciu Tapatalka
Hi Ewa12321,
Thanks for your reply.
I have seen the link, but that is for Android LP isn't it ?
Do you if it's going to work with Android MM ?
Regards.
Enable Mircacast feature on Nexus 9
Has anyone tried successfully to enable this feature?
Renate NST said:
You don't need to modify /system/build.prop
You only need to add that property as persistent and you can do that in /data/property with setprop.
Code:
C:\>adb shell
[email protected]:/ $ su
[email protected]:/ # setprop persist.debug.wfd.enable 1
[email protected]:/ # reboot
On the Nexus 9, after you reboot you need to click the enable Wifi Direct box on the Screen Mirroring setup.
Click to expand...
Click to collapse
SGH-i200 said:
Has anyone tried successfully to enable this feature?
Click to expand...
Click to collapse
it enables it but then crashes as soon as i try and connect to my firetv stick
Hi, I have a problem changing my device model from "ONE E1003" to "X" on Nougat.
Some ROMs like AOSIP,Tesla,Citrus can just simply add/edit "ro.product.model=X" on build.prop and the device name will change just like that.
But on another ROMs like RR,AICP,AEX(my current rom), editing like that won't change the device model. I also tried to use adb command, (adb shell settings put global device_name "X") but it still won't change anything.
Actually it is not really important but seeing my device name on certain apps and in the google play as "OnePlus ONE E1003" sometime really annoy me
If anyone have a better solution, feel free to share with me. Thank you.
So, I found a while back that setting "Profile GPU Rendering" in Developer Options caused all of the UI tearing that was happening in Treble ROMs to go away on my Mate 9; other Huawei devices and ROMs seemed to have the same result - scrolling views stopped tearing.
The problem, of course, is that the property had to be reset on every boot, or you'd end up with UI tearing yet again.
All this module really does is:
Code:
debug.hwui.profile=true
in a Magisk property file.
If you don't want Magisk, you can probably add that directly to /system/build.prop as well. (I haven't tried this yet: I've been trying to leave /system and /vendor alone.)
irony_delerium said:
So, I found a while back that setting "Profile GPU Rendering" in Developer Options caused all of the UI tearing that was happening in Treble ROMs to go away on my Mate 9; other Huawei devices and ROMs seemed to have the same result - scrolling views stopped tearing.
The problem, of course, is that the property had to be reset on every boot, or you'd end up with UI tearing yet again.
All this module really does is:
Code:
debug.hwui.profile=true
in a Magisk property file.
If you don't want Magisk, you can probably add that directly to /system/build.prop as well. (I haven't tried this yet: I've been trying to leave /system and /vendor alone.)
Click to expand...
Click to collapse
FWIW I've already included this workaround in my tree ( https://github.com/phhusson/device_phh_treble/commit/a9a6cba4ddf8227d43cec50fb6d48a410e9369c9)
So my next releases will already do that and won't require your magisk module
phhusson said:
FWIW I've already included this workaround in my tree ( https://github.com/phhusson/device_phh_treble/commit/a9a6cba4ddf8227d43cec50fb6d48a410e9369c9)
So my next releases will already do that and won't require your magisk module
Click to expand...
Click to collapse
Yeah, I figured that'd be the case. I've been using others and they don't include this, so I keep finding myself resetting that flag...
Still nice to have for those ROMs that don't have it.
How ui tearing looks like
I was so happy when i read the post title and then i read phhussons reply and checked the setting myself, so that wont help it.
Im experiencing screen tearing when using the front camera both in snapchat and the huawei stock cam port. P10 C432B371 phhussons PIE v106.
Idk if its directly related to the rom or if its because of my vendor, seeing as you have done some experimentation - maybe you have also run into this issue and know a fix?
Hi !
I am trying to transfer my cat collection from my old phone to my s23. I am using the deprecated adb backup feature to export and import the data in a .ab file. In appearance, everything seems successful, I have the confirmation to restore data on my S23 and the toast notification at the end. However, for some reason my collection is still empty on my phone.
This is something that I have already done successfully from a S8 to a S20, even though the S20 wasn't on the android version where this easter egg was originally available.
I've tried to restore with the package installed as well as making the transfer then installing the package, both without success.
If anyone has done this successfully or has a suggestion, that would be greatly appreciated !
Thanks in advance for your time
does cat control work otherwise, as in new cat arrives?
Not sure what's a cat or a cat collection ;
Backup from older phones to S23 Ultra doesnt work as S23 Ultra uses EROFS File system which breaks restored backups.
Titanium Backup too doesn't work anymore due to this reason. If you have root, you could try Swift Backup.
Yes, cat controls works othewise, I can get new cats on the s23.
Ok thanks for the info on the file system ! Is there any known ways to "bypass" it ?
edit : cat collection is refering to an android easter egg (from nougat IIRC), which is a mini game where you can collect cats with random colors
Also, I am not rooted because I do not need any root feature, I am only missing this data from my old phone, so rooting only for this isn't worth it. I hope there is a solution that doesn't require root...