Database Info

How to install Viper4Andriod on moto X Pure 2015 under Normal mode with all options

I have spent hours trying to figure out how to get Viper4Android working on my moto X pure edition 2015. There is only one thread in the internet discusses this subject http://bit.ly/1j1Gal7 . I tried all the suggested methods in that thread. But none really worked. The results are V4A works only under compatible mode or works but some features are disabled or doesn't work at all.
I even tried some methods suggested for other lollipop phones with the same results.
After lots of trial and error, I finally found a way to have V4A working perfectly on my MXPE under normal mode with all options enabled.
Note: before we start, I assume that you have not messed up the system files on your MXPE. If you have, uninstall any version of V4A on your phone and completely remove any trace of it. Try your best to revert any modifications in the system files done by other methods you have tried.
Important: before you start, take nandroid backup in case something goes wrong.
Let's get down to business:
1- Disable "Audio Effects" using Apps in Setting or Titanium Backup
Reboot
2- Change SELinux to permissive mode using SELinuxModeChanger app
Reboot
3- In Developer options enable "Use AwesomePlayer (deprecated)"
Reboot
4- Install busybox using this app https://goo.gl/tUIwfj Don't use smart install. Just use the normal install
Reboot
5- Use TRWP to flash the following 3 files in the same order:
V4A_MXP.zip
Viper4A_Soundfix_LibFiles.zip
Viper4A_Build_Prop_Tweaks.zip
Wipe cache & davik cache and reboot
6- Open V4A and install the drivers and reboot
7- By now you should have a working V4A under normal mode but without neon support. Continue with next steps to fix this
8- Open V4A and uninstall drivers and reboot
9- We want now to uninstall V4A but since it's installed as a system app, we need a special app to do this. I used Titanium Backup
Reboot
10- Install the normal Viper4Android apk not the zip Must be installed as a user app not a system app
11- Open V4A and install the drivers. I chose the Power Saving but you can go with Super Audio Quality if you want
Reboot
Congratulation... You have now a perfectly working V4A on your moto X PE/Style 2015 with all the options enabled under normal mode

Glad you took the time to dive into this. In the middle of closing on a house also previous 2 phones were defective. so I didn't time to dive in. Currently using xtreme music mod flawlessly. Will definitely use this on next clean flash. Any issues between stock or cm running using same method. Thanks for your hard work.
Edit... forgot to mention that I'm op from viper confirmed thread.

works great thanks for you time and also to share it with us

Delete

I got it to work a while ago by flashing xtreme music mod but first I installed v4a from their website,installed driver, then flashed xtreme music mod. So I had both and then I disabled v4a from the apk. And kept the one from xtreme music mod and works under normal mode.
But v4a on this phone has issue like gets lost somewhere in ram because sometimes effects are not that strong after I reboot they are stronger.
Sent from my XT1575 using Tapatalk

Got it working, but seems to partially break aux when connecting to a car need to plug in really slow to get it to work (been the same for every V4a I've tried) Thanks for the work.

I have flashed as suggested. Works fine.

I just moved from stock to AICP and this did not work to enable neon but xtrememusic mod won't enable neon as well (did work on stock)
However even with neon off under normal mode I don't see any difference in quality. Maybe it's just me.

elevatorguy said:
Got it working, but seems to partially break aux when connecting to a car need to plug in really slow to get it to work (been the same for every V4a I've tried) Thanks for the work.
Click to expand...
Click to collapse
Works great here with aux. No problems whatsoever.

patt2k said:
I just moved from stock to AICP and this did not work to enable neon but xtrememusic mod won't enable neon as well (did work on stock)
However even with neon off under normal mode I don't see any difference in quality. Maybe it's just me.
Click to expand...
Click to collapse
Tested on stock rom. Not sure about other roms.

Pretty crazy all the hoops to go through to get it working but you're the man...it works. Thanks

Works part of the time using it in my car on audio jack. When listening via Google Play Music, it won't be active and then suddenly the volume drops like a notification is coming through and it pops back up and I can tell that Viper became active. Strange. Followed all the steps to the letter. Even checked 'force Viper' when I noticed this happening and no change, still does it. On stock rom, unlocked.

Somebody try to run this process on MM?
Sent from my XT1575 using Tapatalk

Was just about to ask that myself I'm having trouble getting v4a to work on MM. If anyone could tell me the process if they have this working could you kindly let me know it would be much appreciated
Sent from my XT1575 using XDA Premium HD

k3mik4l said:
Was just about to ask that myself I'm having trouble getting v4a to work on MM. If anyone could tell me the process if they have this working could you kindly let me know it would be much appreciated
Sent from my XT1575 using XDA Premium HD
Click to expand...
Click to collapse
Have you tried this method?
Sent from my XT1575 using Tapatalk

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Method still working on MM.
Sent from my XT1575 using Tapatalk

I am on MM, rooted. I do not have any eq settings in sound / notification is that normal? Also in Dev options, Use Awesome player (depricated) is not there.
Going to attempt install anyway and see how it goes.

lafester said:
I am on MM, rooted. I do not have any eq settings in sound / notification is that normal? Also in Dev options, Use Awesome player (depricated) is not there.
Going to attempt install anyway and see how it goes.
Click to expand...
Click to collapse
This works great. Thanks!
For anyone having issues with Viper sometimes, and opening the Viper app fixes it, a tasker profile should fix it.
I put a task to run the following shell command whenever my headphones or bluetooth stereo are connected:
am startservice com.vipercn.viper4android_v2/.service.ViPER4AndroidService
Might need to run as root.. not sure.
Also, using App Settings with Xposed and checking Resident should keep it from being killed from memory.
You can find the Lollipop version for App Settings here.

I just flashed xtrememusic mod and to my surprise out of the box neon is not enabled. That would be easiest way to do it. So far everything is good.
Sent from my XT1575 using Tapatalk

much for simplified process
Have an extremely simplified process I have discovered that is at least working on my TruePureX 2.2 install (so Marshmallow deodexed ROM). This method has the MAJOR benefit of leaving SELinux in enforcing, that's what the 4th zip I have added to the process accomplishes! This fix was created by a user named maximumentropy. His original post is here.
http://forum.xda-developers.com/showpost.php?p=61242973&postcount=18854
This script requires the use of SuperSU as your root solution so be sure you have root established with it before continuing (not tested on systemless root)
*Note* Because of this fix it is also possible to leave Viper4Android as system app and it will asked you to install the driver of your choice immediately after flashing it the FIRST time. Saving tons of restarts. Also we can skip enabling awesomeplay as well. (not even possible on Marshmallow from what I gather anyhow)
So without further delay. Here is the updated process
1. Disable "Audio Effects" using Apps in Setting or Titanium Backup. No need to restart
2. Install busybox using the app "busybox" from play store. consider a purchase just to support the dev. Do not use smart install!
NOW Reboot to recovery
3. Use TRWP to flash or sideload the following 4 files in the following order:
a. V4A_MXP.zip http://bit.ly/1O8Mker
b. Viper4A_Soundfix_LibFiles.zip http://bit.ly/1MdLInf
c. Viper4A_Build_Prop_Tweaks.zip http://bit.ly/1NSCCid
d. ViPER4Android-supolicy.zip https://www.dropbox.com/s/k9cnruw2e1t1d4t/ViPER4Android-supolicy.zip?dl=0
Now... wipe just cache (no need to wipe dalvik, takes too long and not needed) and reboot
4. Now Viper4Android will be installed as system app so open it up. Be sure to grant it Root permission via SuperSU prompt, it will ask you which driver you would like to install. Select one of the 3 options I personally use "Super Audio Quality"
Reboot one more time and viola
You now have a fully functional Viper4Android and you have not compromised your kernel security by changing SELinux policy. Again we can avoid the messiness of uninstalling the system app and reinstalling as user app this way saving time. This is fully functional including NEON support!!!
I hope this simplifies the process for everyone, certainly alot quicker this way! If OP would like to update the first post please feel free.

[Q] ViPER4ANDROID?

Is there anyone out there managed to get viper4android working? I've tried using lolliviper, doesn't work. I've tried changing audio_effect.conf, doesn't work, every time status is abnormal can't seem to work on S7.
Shout out, Viper4android is the best mod ever!

yes it works for me, install the latest apk, and flash this
http://www104.zippyshare.com/v/K1dgN9iU/file.html
also disable or remove Samsung soundalive.
Tapatalked from GALAXY S7

[email protected] said:
yes it works for me, install the latest apk, and flash this
https://www.dropbox.com/s/k9cnruw2e1t1d4t/ViPER4Android-supolicy.zip?dl=0
also disable or remove Samsung soundalive.
Tapatalked from GALAXY S7
Click to expand...
Click to collapse
Hi bro, just do these steps will do? I need not install busybox? Will do this once I get back home and will update!

nansensical said:
Hi bro, just do these steps will do? I need not install busybox? Will do this once I get back home and will update!
Click to expand...
Click to collapse
yes you need busybox too
Tapatalked from GALAXY S7

[email protected] said:
yes you need busybox too
Tapatalked from GALAXY S7
Click to expand...
Click to collapse
Still cant get it to work.
1. Install Busybox.
2. Install Viper4android 2.4.0.1
3. Disable Soundalive using Titatnium
3. Reboot and flashed the file that you gave
4. Installed Viper4android drivers and reboot again
Status is normal with neon BUT music sounds the same thru Spotify, Google Music, VLC. no change in sound effects.
5. Disable Adapt Sound. Still the same
Did I skipped any steps?

@nansensical
note sure about these apps as I use PowerAMP but I found this:
https://www.reddit.com/r/Nexus5/comments/20zubh/viper4android_not_working_with_spotify/

[email protected] said:
@nansensical
note sure about these apps as I use PowerAMP but I found this:
https://www.reddit.com/r/Nexus5/comments/20zubh/viper4android_not_working_with_spotify/
Click to expand...
Click to collapse
I've tried all that. I'm exhausted. Still can't get it to work.

nansensical said:
I've tried all that. I'm exhausted. Still can't get it to work.
Click to expand...
Click to collapse
Me neither. Faaack
Sent from my Galaxy 1 Turbo

Anybody managed to install viper4android?

this is how it looks for me when playing music with PowerAMP
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
try flash this file instead for previous
http://www104.zippyshare.com/v/K1dgN9iU/file.html
here is the APK: http://www.mediafire.com/download/ar5men9o5ar7inb/ViPER4Android_FX_v2401_A4.x-A6.x.apk
also try with a Music player, for example PowerAMP and see if it works.
Tapatalked from GALAXY S7

[email protected] said:
this is how it looks for me when playing music with PowerAMP
try flash this file instead for previous
http://www104.zippyshare.com/v/K1dgN9iU/file.html
here is the APK: http://www.mediafire.com/download/ar5men9o5ar7inb/ViPER4Android_FX_v2401_A4.x-A6.x.apk
also try with a Music player, for example PowerAMP and see if it works.
Tapatalked from GALAXY S7
Click to expand...
Click to collapse
No sir. Poweramp does not work either. I'm tried Spotify, Google Music, Sony Walkman App, Poweramp, VLC, ES music player..
I'm not going to sleep tonight till I get to fix this.

in PowerAMP have you turned off the direct volume control under settings/audio/Advanced Tweaks?

[email protected] said:
in PowerAMP have you turned off the direct volume control under settings/audio/Advanced Tweaks?
Click to expand...
Click to collapse
Ok. I did exactly as u said. It works. On Poweramp. Now just need to figure out how to work on Spotify.. thank you

The Viper4Android need a rooted device and kernel permissive?

abelrhd said:
The Viper4Android need a rooted device and kernel permissive?
Click to expand...
Click to collapse
yes and yes but with that zip file you don't need permissive kernel.
Tapatalked from GALAXY S7

nansensical said:
Ok. I did exactly as u said. It works. On Poweramp. Now just need to figure out how to work on Spotify.. thank you
Click to expand...
Click to collapse
[email protected] said:
yes and yes but with that zip file you don't need permissive kernel.
Tapatalked from GALAXY S7
Click to expand...
Click to collapse
Thanks friend I have a S7 edge without root. So, I cannot use the v4a for this. Do you know a great alternative for v4a without root? PowerAmp it's a great app but only use in music but not in videos.
Thanks!

http://forum.xda-developers.com/galaxy-s7/how-to/guide-how-to-viper4android-t3337426
Got V4A fully working (Spotify, Google play music etc.)
I've tried the same steps mentioned in the s6 edge forum HERE
Do a full backup first!
These steps worked for me:
1. Install Busybox.
2. Install Viper4Android 2.4.0.1
3. Grant Viper4Android permissions to write (Settings ->Applications -> Applicationmanager -> V4A -> Permissions -> Enabled)
4. Delete SoundAlive with RootExplorer (or disable/freeze it with Titanium Backup)
5. Go to /system/etc/ and rename audio_effect.conf to audio_effect.conf.bak
6. Download the modified audio_effect.conf HERE and copy it to /system/etc/ and /vendor/etc/
7. Set permissions of the new config file to rw-r-r (0644) (important! Otherwise --> Bootloop)
8. Reboot
9. Start V4A and install the drivers
10. Reboot
DONE

NQNH said:
http://forum.xda-developers.com/galaxy-s7/how-to/guide-how-to-viper4android-t3337426
Got V4A fully working (Spotify, Google play music etc.)
I've tried the same steps mentioned in the s6 edge forum HERE
Do a full backup first!
These steps worked for me:
1. Install Busybox.
2. Install Viper4Android 2.4.0.1
3. Grant Viper4Android permissions to write (Settings ->Applications -> Applicationmanager -> V4A -> Permissions -> Enabled)
4. Delete SoundAlive with RootExplorer (or disable/freeze it with Titanium Backup)
5. Go to /system/etc/ and rename audio_effect.conf to audio_effect.conf.bak
6. Download the modified audio_effect.conf HERE and copy it to /system/etc/ and /vendor/etc/
7. Set permissions of the new config file to rw-r-r (0644) (important! Otherwise --> Bootloop)
8. Reboot
9. Start V4A and install the drivers
10. Reboot
DONE
Click to expand...
Click to collapse
I can confirm this works! Thanks a lot! Very happy S7 owner here!

I have done everything as above but the driver status is showing as not enabled. Status: abnormal, Audio format: unsupported.
Just ended up hacking the volume another way so it's not an issue.

NQNH said:
http://forum.xda-developers.com/galaxy-s7/how-to/guide-how-to-viper4android-t3337426
Got V4A fully working (Spotify, Google play music etc.)
I've tried the same steps mentioned in the s6 edge forum HERE
Do a full backup first!
These steps worked for me:
1. Install Busybox.
2. Install Viper4Android 2.4.0.1
3. Grant Viper4Android permissions to write (Settings ->Applications -> Applicationmanager -> V4A -> Permissions -> Enabled)
4. Delete SoundAlive with RootExplorer (or disable/freeze it with Titanium Backup)
5. Go to /system/etc/ and rename audio_effect.conf to audio_effect.conf.bak
6. Download the modified audio_effect.conf HERE and copy it to /system/etc/ and /vendor/etc/
7. Set permissions of the new config file to rw-r-r (0644) (important! Otherwise --> Bootloop)
8. Reboot
9. Start V4A and install the drivers
10. Reboot
DONE
Click to expand...
Click to collapse
Which busybox? I've never had success with getting busybox to work... Please give me a link and explain what settings i need to set?
---------- Post added at 09:19 PM ---------- Previous post was at 09:06 PM ----------
There are way too many conflicting instructions here. Which one is the best?

[V4A] Fix for 'Processing: No' while using Magisk

Disclaimer:
• First, you have to follow the basic rules of V4A such as no other audio mods (AudioFX, MusicFX,...), uncheck direct control volume in Poweramp...
• Since Oreo, I only flash this Magisk module and I no longer have to follow the below steps.
1. THE PROBLEM
• You are using ViPER4Android app and the V4A module from the official repo of Magisk.
• Driver is installed, V4A is enabled but Processing is stuck at NO!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. THE SOLUTION
• Move /magisk/v4a/system/etc/audio_effects.conf to /magisk/v4a/system/vendor/etc/audio_effects.conf (check the permissions).
Note : overwrite the existing file or add the extension .bak
• Reboot.
Now start your music app and check the driver status screen of V4A. You should have this:
Enjoy
I found this solution in one of Magisk threads. Hope it will help other OP3T users.

Working perfect

Primokorn said:
1. THE PROBLEM
2. THE SOLUTION
• Move /magisk/v4a/system/etc/audio_effects.conf to /magisk/v4a/system/vendor/etc/audio_effects.conf (check the permissions).
• Reboot.
Now start your music app and check the driver status screen of V4A. You should have this:
.
Click to expand...
Click to collapse
I can confirm this works..Means i dont have to use another magisk module i found where the bass clips heavily over BT headphones. +1!

Same problem on the OG OP3. All I had to do was download the module and flash it in TWRP.

Confirmed working fine. I had a /magisk/v4a/system/vendor/etc/audio_effects.conf already, but moved the /magisk/v4a/system/etc/audio_effects.conf to that folder overwriting the other one. Works!

I did this but audio doesn't play but it says processing. I'm using the black player app as my music player and when i try to play music nothing comes out
Edit: wow, I'm actually dumb. Didn't realize that after the reboot the volume gets turned all the way down. Works fine lol

showofdeth said:
Same problem on the OG OP3. All I had to do was download the module and flash it in TWRP.
Click to expand...
Click to collapse
The official Magisk module and the one from Viper4Arise didn't help me either. The same with Viper4Arise zips/modules.
This 'trick' was the only solution that worked for me.

It worked thnx?

It can be achieved through a flashable zip. Let me know if you are interested (easier clean flash process)
Replacing /magisk/v4a/system/vendor/etc/audio_effects.conf survives a dirty flash

Primokorn said:
It can be achieved through a flashable zip. Let me know if you are interested (easier clean flash process)
Replacing /magisk/v4a/system/vendor/etc/audio_effects.conf survives a dirty flash
Click to expand...
Click to collapse
Yes please.

Yes too.

Primokorn said:
It can be achieved through a flashable zip. Let me know if you are interested (easier clean flash process)
Replacing /magisk/v4a/system/vendor/etc/audio_effects.conf survives a dirty flash
Click to expand...
Click to collapse
yes please !
---------- Post added at 10:38 PM ---------- Previous post was at 10:37 PM ----------
Primokorn said:
1. THE PROBLEM
• You are using ViPER4Android app and the V4A module from the official repo of Magisk.
• Driver is installed, V4A is enabled but Processing is stuck at NO!
2. THE SOLUTION
• Move /magisk/v4a/system/etc/audio_effects.conf to /magisk/v4a/system/vendor/etc/audio_effects.conf (check the permissions).
• Reboot.
Now start your music app and check the driver status screen of V4A. You should have this:
Enjoy
I found this solution in one of Magisk threads. Hope it will help other OP3T users.
Click to expand...
Click to collapse
i can't find .... /magisk/v4a/system/etc/audio_effects.conf ??? I'm using a root explorer to look for it.

Edit: My problem with missing v4a app icon solved. I realised that I had to download and install the apk after installing the v4a module in magisk manager.
On topic, the driver fix worked. Thanks a lot OP.

This works on op3 as well. Thanks

I can't replace the conf files anymore on Magisk 11.6... Flashable ZIP plz ^^

I struggle with magisk. The scripts I usually flash don't work here.
I'll try to create a working script...

Error.

where is this folder and file located????

alexdonwarez said:
where is this folder and file located????
Click to expand...
Click to collapse
The paths are mentioned in OP...

Primokorn said:
The paths are mentioned in OP...
Click to expand...
Click to collapse
yeah but im not able to find it "/magisk/v4a/system/etc/audio_effects.conf" is it located in the root directory.. In my freedom rom i can find only magisk folder with some arise sound config files, no v4A folder.

[OOS][Oreo] Enable Google Daydream VR Support

For Oxygen OS - 5.1.3 Oreo on Oneplus 5T.
Flash in TWRP after making a backup.
Please read all info below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
!!! CAUTION !!!
Use at your own risk. Backup before flashing.
I am not responsible for bricked devices,
thermonuclear war or your monkey dancing samba!
IMPORTANT INFO:
Flashing
The installer changes one file. It overwrites \system\etc\permissions\handheld_core_hardware.xml
with an updated version to enable the Google Daydream support.
Removing
There is also the remover ZIP. It restores the stock OOS 5.1.3 permission file.
After flashing - get ready
You wiped your cache and dalvik and boot the device.
Go to your application list and show system apps.
Delete cache and data of the Play Store app so Daydream is
downloadable via Play Store. Open Play Store,
do not forget to set your previous Play Store configuration and install:
• Daydream
• Daydream Keyboard
• Google VR Services
Some reported that setting to skip all intros in Daydream developers options
fixed problems that occured.
Start, set the other config which is needed and try. For me it works fine.
The only thing that is a bit sad is that the 5T with full HD gives a not very sharp display view - it is grainy.
๏[-ิ_•ิ]๏

Does it work on 5.0.3?
Also, does it trigger the 'safetynet'?

lockywolf said:
Does it work on 5.0.3?
Click to expand...
Click to collapse
Actually the file did not change for 5.0.3, but I changed the ZIP filename to clearify.
lockywolf said:
Also, does it trigger the 'safetynet'?
Click to expand...
Click to collapse
I don't think so.
By the way; it is a tiny mod that does no heavy system tweaking.
I made it just for convenience so users do not need to use a root explorer and text editor for the changes.

Thank you.
Just FYI, it's not working in Oreo Resurrection Remix.
I can open Daydream without issue.
But as soon as I put my OP5T into the headset, the OP5T hard reboots.
I attached a logcat in case anyone is interested.

CZ Eddie said:
Thank you.
Just FYI, it's not working in Oreo Resurrection Remix.
I can open Daydream without issue.
But as soon as I put my OP5T into the headset, the OP5T hard reboots.
I attached a logcat in case anyone is interested.
Click to expand...
Click to collapse
This is happening to me as well on AICP. Wanting this to work lol. Please keep me updated if you find anything out!

CZ Eddie said:
Just FYI, it's not working in Oreo Resurrection Remix.
Click to expand...
Click to collapse
bschmidy10 said:
Please keep me updated if you find anything out!
Click to expand...
Click to collapse
See, I am not a real dev... just some guy with basic knowledge. I updated the ZIP and made two new for the ROMs you use.
Try them, but read the OP/CAUTION section please.
The attached ZIPs contain the modified file from your ROMs which are different in one line compared to OOS.
Plus I added a mod for the build.prop to maybe make it work.
If all fails I guess this try was just an interesting waste of time,
and someone more advanced would have to figure out a possible solution.
•••

Thank you!
I'm sorry but my Resurrection Remix Oreo still forced rebooted when I put the phone into the headset. I attached another logcat if you're interested.

CZ Eddie said:
Thank you!
I'm sorry but my Resurrection Remix Oreo still forced rebooted when I put the phone into the headset. I attached another logcat if you're interested.
Click to expand...
Click to collapse
As I wrote I can not help any further.
I installed Google VR keyboard, Daydream, VR services etc. and tested some apps under OOS 5.0.3, but all without VR hardware - I do not own the headset/controller. I enabled developer options on Daydream and skipped all intros, read that elsewhere.

I've got the same problem, RR 8.0.1. Logcat implies that the ACore process lacks permissions to access the VR hardware, and crashes upon attempting it, taking the entire systemui and all of its children with it.
I'm in the process of experimenting and seeing if it's possible to grant those permissions somehow..

Anybody got it working? I saw the set today at a store and thought about buying it...

This has always worked for me: https://www.xda-developers.com/force-daydream-vr-compatibility/
never needed to change the device name, just added the 2 lines and rebooted. Daydream apps download and update via playstore as well.

OTA Updates
Does unlocking bootloader, flashing twrp and installing this, cause problems with OTA Updates or something?

aschi2403 said:
Does unlocking bootloader, flashing twrp and installing this, cause problems with OTA Updates or something?
Click to expand...
Click to collapse
Did you face problems with OTA? I will update this if I find the time.
Gesendet von meinem ONEPLUS A5010 mit Tapatalk

t-ryder said:
Did you face problems with OTA? I will update this if I find the time.
Gesendet von meinem ONEPLUS A5010 mit Tapatalk
Click to expand...
Click to collapse
No I din't face any, I just wanted to know if there are known problems before I install this.
But now I have a new Question. I thought to not mess around with OTA as I read on some XDA-Thread that TWRP might keep official OTA from working, I would just unlock the bootloader and then boot into TWRP with "fastboot boot recovery.img", flash this zip and reboot into stock OOS with this guide https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592 on.
But then on the twrp Website I read that "swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel" so my question is, can I flash this zip without messing around with OOS, I don't really want to install a custom kernel, because for now I just want the stable stock rom.

aschi2403 said:
No I din't face any, I just wanted to know if there are known problems before I install this.
But now I have a new Question. I thought to not mess around with OTA as I read on some XDA-Thread that TWRP might keep official OTA from working, I would just unlock the bootloader and then boot into TWRP with "fastboot boot recovery.img", flash this zip and reboot into stock OOS with this guide https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592 on.
But then on the twrp Website I read that "swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel" so my question is, can I flash this zip without messing around with OOS, I don't really want to install a custom kernel, because for now I just want the stable stock rom.
Click to expand...
Click to collapse
I tried it and I didn't face any of my concerns, but I'm on OxygenOs 5.1.2 and after flashing this, wiping cache, then reboot. Daydream App after a long black screen shows me, that my device isn't compatible with Daydream. Did I do something wrong or is it because of the OxygenOS Version?

EDIT: see post #19

I just bought a Daydream Set (v1) for like 20$ second hand online. Will report regarding further testing when the set has arrived.

Updated for Oxygen OS 5.1.3

Got my headset and all works fine. The image is a bit grainy because 5T has only full HD.
No need for an installer with build.prop changes. I tested the system changes and updated the installer and remover.
If you have tried the old installer/enabler you may restore your build.prop using a root file explorer. It is located in /system (.bak file).
Have fun.

M.Sami said:
never needed to change the device name, just added the 2 lines and rebooted.
Click to expand...
Click to collapse
Yes, you are right.

[HELP NEEDED] Camera2 Api cannot be enabled in my Redmi Note 6 Pro.

Hello everyone!
My problem is I cannot enable Camera2 Api on my Redmi note 6 Pro in any method I've tried so far. (I didn't try rooting and editing the build prop cuz I don't want to root my device yet.) I'm not an expert in these cases guys but I watched and read many tutorials about this and tried almost all methods but the camera2 api is still not enabled for my device for some reason.
*Yes! my bootloader is unlocked!
*Yes! I have set up all the usb drivers and adb on my PC!
*No! I haven't installed any custom recovery permanently!
Firstly I tried enabling it by adb using the following commands (While TWRP image is booted);
adb shell
setprop persist.vendor.camera.HAL3.enabled 1
this didn't give me any error but after I restarted the phone and checked, Camera2 Api wasn't enabled.
Then I tried to flash a zip file to enable it. I've tried many different zip files but none worked. ( I copied the zip files to my SD card and selected them from there because when I temporarily booted into TWRP, it didn't recognize any file in my internal storage. It just showed my internal storage is 0MB! then I mounted my SD card then TWRP recognized the zip files in there.) First I flashed a "Disable DM Verity Force Encrypt" zip and it gave me "Successful!". Then I tried to flash the "Camera2 Api" zip but it gave me "Failed!". I tried 5-6 different zips from the Internet (meant for my device) but every one of them gave an error.
So..yup..that's my problem. I really really want to install G Cam on my device but I can't understand where is the error. Everyone seems to success with this process but for some reason it doesn't work for me. I'm afraid to do anything which breaks OTA updates either. I don't know this area a lot so any help on this means a lot to me. Sorry for the long post guys. Thanks a lot in advance!
Have a nice day everyone!
(P.S. - Please find the attached images for more info. Thanks!)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

thats my idea:
last month i try like that...first write hal3=1 to the buildprop.than restart..
than disable again (hal3=0).restart..
finally enable again hal3=1 than restart..its worked for me like that.Interested solution ... some users (mi 8 lite) tryed my solution but didn't work.Someones tryed magisk module 2-3 times than worked no any issue

[email protected] said:
thats my idea:
last month i try like that...first write hal3=1 to the buildprop.than restart..
than disable again (hal3=0).restart..
finally enable again hal3=1 than restart..its worked for me like that.Interested solution ... some users (mi 8 lite) tryed my solution but didn't work.Someones tryed magisk module 2-3 times than worked no any issue
Click to expand...
Click to collapse
Thanks for the reply!
I haven't rooted my phone yet so I'm unable to try this solution at the moment friend since I can't edit the build.prop. But if there aren't any other solution I will definitely root my device and try this!
Thanks again for your concern!

Charith Lekamge said:
Thanks for the reply!
I haven't rooted my phone yet so I'm unable to try this solution at the moment friend since I can't edit the build.prop. But if there aren't any other solution I will definitely root my device and try this!
Thanks again for your concern!
Click to expand...
Click to collapse
try with root solution.(with magisk). You can unistall it. buildprop solution better than others.

[email protected] said:
try with root solution.(with magisk). You can unistall it. buildprop solution better than others.
Click to expand...
Click to collapse
Hello again!
I tried editing build.prop my friend and it worked!! Just as you said I firstly set the prop value to 0 and restart and then again set it to 1 and restart and it worked magically! Thank you so much for your help friend!

you are welcome

[email protected] said:
you are welcome
Click to expand...
Click to collapse
Hello there can you help me eneble the camera2api on miui V10.3.3.0

Rei Shu said:
Hello there can you help me eneble the camera2api on miui V10.3.3.0
Click to expand...
Click to collapse
its easy.if ur bootloader unlocked:first install twrp on ur device.than install magisk apk on your system or install with twrp(flash zip).Than install buildprop app on the app store.Open app.Than search hal3=0 word on the buildprop app. thats it
You can install magisk app on the apk like this.install magisk app-open app-than click download zip.You can install that zip on the twrp interface or search on the google (magisk.zip)

[email protected] said:
its easy.if ur bootloader unlocked:first install twrp on ur device.than install magisk apk on your system or install with twrp(flash zip).Than install buildprop app on the app store.Open app.Than search hal3=0 word on the buildprop app. thats it
You can install magisk app on the apk like this.install magisk app-open app-than click download zip.You can install that zip on the twrp interface or search on the google (magisk.zip)
Click to expand...
Click to collapse
It was my first time unlokcing my phone and installing twrp etc. Last phone which I was rooting swtiching to roms was the legendary HTC HD2.
I did what you explain to this person I swtich hal3=1 to 0 and than again to 1 and it worked

Rei Shu said:
It was my first time unlokcing my phone and installing twrp etc. Last phone which I was rooting swtiching to roms was the legendary HTC HD2.
I did what you explain to this person I swtich hal3=1 to 0 and than again to 1 and it worked
Click to expand...
Click to collapse
last xiaomi update was **** dude.hal3=1 but nothing works on gcam.my solution works every redmi note 6 phone without no problem.
but you r trying first time.You can install gcam without any problem while hal3=1

[email protected] said:
last xiaomi update was **** dude.hal3=1 but nothing works on gcam.my solution works every redmi note 6 phone without no problem.
but you r trying first time.You can install gcam without any problem while hal3=1
Click to expand...
Click to collapse
Xiaomi could make this device run a lot more smoother.. still the full screen gestures are lagging kinda :/ I was planning on installing some rom but from what im reading all of them are full of bugs etc.
Btw what version of Gcam you using I found some version where night mode works on front camera and the back camera without any problem but when HDR is off its not taking pictures until i turn it on :/

Rei Shu said:
Xiaomi could make this device run a lot more smoother.. still the full screen gestures are lagging kinda :/ I was planning on installing some rom but from what im reading all of them are full of bugs etc.
Btw what version of Gcam you using I found some version where night mode works on front camera and the back camera without any problem but when HDR is off its not taking pictures until i turn it on :/
Click to expand...
Click to collapse
MGC_6.2.024_BSG_Arnova-based_v.0.2_TlnNeun.apk
im using this version without any problem.night sight and hdr works good.