Due to complaints that the addon does not work, I have now removed it from the forum.
Unfortunately, I can not understand that it does not run, because I had no problems on two devices.
If someone still wants to test or has questions he can send me a PN.
The topic may be closed.
With kind regards
Ramme
Spoiler: Old Guide
Use on your own risk.
Hello everyone, I found a post on the OnePlus8Pro forum about Dolby Atmos.
There sirioo posted a Magisk file which adds the full Dolby Atmos to the system. (Made for the OP8Pro!)(Thanks for this!).
I tested this on my OnePlus 8T and found that Dolby Atmos works fine.
For those who would also like to have the full program, I now share my experience.
Instructions: (Root(Magisk) required + Audio Modification Library + USB debugging enabled) !!!
Step 1: Download "SDK Platform Tools", unpack it. Go to the folder and type "CMD" in the top bar. Now your console will open.
Step 2: Make sure that your phone has USB debugging enabled and allowed to the computer (can be enabled in the developer options). Now type the following command: (The Phone must stay ON during the process!)
adb shell pm uninstall --user 0 com.oneplus.sound.tuner
#This removes the Dolby Atmos tuner present on your device.#
Info: After the command (Step:2) you can check in the Settings>Sound&Vibration>> under "Sound effects and modes", there should be now the Dolby-setting disappeared.
Step 2.1: Restart your Phone.
Step 3: Now Download "DolbyAtmosOOS" and put it on your device. (or download the file from my attachment.) Now open Magisk and load the file from your storage and restart your device. Voilà Dolby Atmos can now be enjoyed to the fullest.
How do I get back to the default? > Uninstall the Magisk addon, restart your device.
Tested on OP8T - OOS 11.0.7.10.KB05BA (EU) - 03.20.2021
Tested on OP8T - OOS 11.0.8.12.KB05BA (EU) - 04.11.2021
A little video from me to show that Dolby works under OOS 11.0.8.12.KB05BA !
Pros of DolbyAtmos Full?
More and more detailed setting options than with the system's own.
Spoiler: Screenshots:
{
"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"
}
Edit: 04.11.2021
In the meantime changed my ROM back and forth a few times. (for testing purposes on my part), I repeated today (04.11.2021) the installation of DolbyAtmos according to my instructions and it worked successfully. I am currently on OP8T OOS 11.0.8.12.KB05BA (Model: KB2003)
To the ones who say it doesn't work, I can only say that you not exactly following the instructions or you are on a custom rom.
Uforuently mine did not flash and said failed in Magisk.
OnePlus 7T Pro 5G Running AOSIP
Dopewaffles said:
Uforuently mine did not flash and said failed in Magisk.
OnePlus 7T Pro 5G Running AOSIP
Click to expand...
Click to collapse
think it's because you're running AOISP?
Is this working together with V4a?
vibrantliker said:
think it's because you're running AOISP?
Click to expand...
Click to collapse
Could very well be.either way it screwed it up :/
My instructions are only for the Official OOS, to all other custom roms I can not say anything, the 8Pro forum which I linked above in the text is only for information where I got the Magisk file.
I have performed the procedure according to my instructions on two OnePlus8T, on both devices DolbyAtmos works successfully.
For custom roms based on OOS-vendor, there is also an alternative here in the forum.
@vibrantliker
Yes, it runs together with Viper4Android.
Dopewaffles said:
Could very well be.either way it screwed it up :/
Click to expand...
Click to collapse
did it brick your phone or just not flash in Magisk?
vibrantliker said:
did it brick your phone or just not flash in Magisk?
Click to expand...
Click to collapse
So I installed it and everything was just fine. After finding out it did not work (kept crashing) I decided to remove it from Magisk and then when my phone rebooted it got stuck in a bootloop. Eventually I dirty flashed my ROM back and got everything going again after doing more tweeks, but that was the extent of that.
But 8T already has Dolby Atmos. Am I missing something here?
Unfortunately I can't install this on OOS11. Anyone with the same problem?
Adityaveer Rathee said:
But 8T already has Dolby Atmos. Am I missing something here?
Click to expand...
Click to collapse
Whether you miss something I can not answer, but I can tell you that they do not have the same level of accuracy (setting options) in the official DolbyAtmos.
HubertGT said:
Unfortunately I can't install this on OOS11. Anyone with the same problem?
Click to expand...
Click to collapse
Did you follow my steps exactly?
Unfortunately, I did not create the package myself and cannot provide any support in this regard.
i did all of these steps and it installed but there is no problem i dont think it works correctly. when i disable dolby i didnt notice any difference (7T Pro OOS 11 , Stable)
This app has been reported multiple times as NOT working. I don't suggest anyone download it.
Dopewaffles said:
This app has been reported multiple times as NOT working. I don't suggest anyone download it.
Click to expand...
Click to collapse
Yep, can confirm.
The app is not working as it should. Don't install it.
Dopewaffles said:
This app has been reported multiple times as NOT working. I don't suggest anyone download it.
Click to expand...
Click to collapse
epr said:
Yep, can confirm.
The app is not working as it should. Don't install it.
Click to expand...
Click to collapse
If you could at least tell me how the app doesn't work, I could at least help.
Since all I hear is that it doesn't work, I can't do anything.
The next question would be to clarify what kind of smartphone you use? What version of OOS are you on?
I have so far only read out that it does not work on a 7tpro and on a custom rom, but from OOS I have heard nothing?
*
Attached I have just made the trouble to create a small video, which shows that Dolby works.
I mention again that I did not create the Magisk Dolby file, but only found out that it works with the OnePlus8T on OOS!
Ramme said:
If you could at least tell me how the app doesn't work, I could at least help.
Since all I hear is that it doesn't work, I can't do anything.
The next question would be to clarify what kind of smartphone you use? What version of OOS are you on?
I have so far only read out that it does not work on a 7tpro and on a custom rom, but from OOS I have heard nothing?
*
Attached I have just made the trouble to create a small video, which shows that Dolby works.
I mention again that I did not create the Magisk Dolby file, but only found out that it works with the OnePlus8T on OOS!
Click to expand...
Click to collapse
I am using KB2003, OOS 11.0.8.12 KB05BA
Yes, it looks like it's working. I can move the sliders and set the different modes BUT no matter what I do, it makes absolutely no difference to the sound. And the volume controls are no longer working, volume keeps at one fixed level, the sliders are moving but nothing happens. Demo mode is also not working.
Besides this I don't see any advantages against the built-in Dolby Atmos except the equalizer which is also not very useful because there is no option to save the settings as a preset.
Mine is working on H2OS system, thank you.
epr said:
I am using KB2003, OOS 11.0.8.12 KB05BA
Yes, it looks like it's working. I can move the sliders and set the different modes BUT no matter what I do, it makes absolutely no difference to the sound. And the volume controls are no longer working, volume keeps at one fixed level, the sliders are moving but nothing happens. Demo mode is also not working.
Besides this I don't see any advantages against the built-in Dolby Atmos except the equalizer which is also not very useful because there is no option to save the settings as a preset.
Click to expand...
Click to collapse
Yep, you are right, I installed it successfully and it was not working when I changed the configurations, and after I put it into background application and it was stuck.
Edited
not working on oos 11 8t
Related
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.
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.
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.
{
"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"
}
Moto Z Play
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the Moto Z Play.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
addison
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
The EQ Apps for Audio Mods (eg. JBL2 App) won't work, and will crash.
Audio Mods have no alarm or notification audio through them.
Camera Mods don't (and won't ever) work.
Volume may be lowered when locking and unlocking the device
Non-original touchscreens may fail to respond
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Official Lineage OS builds for addison ship with full Project Treble compatibility! Flash GSI's to your heart's content after flashing Lineage. Please don't report GSI bugs here, report them instead to the GSI's maker.
Code:
Technical details on our Treble implementation:
Treble is enabled with VNDK30, and VNDK runtime enforcement. VNDK runtime enforcement means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run GSIs. without need for hacks or additional flashable zips. We relabeled /oem to /vendor (as /oem isn't wasn't used in custom ROMs anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image.
Kernel Source: https://github.com/LineageOS/android_kernel_motorola_msm8953
Hi there, just tried this new ROM and it is pretty nice that most functions are working well, really appreciate your maintainance!
However, this ROM has the same bugs as the previous AICP one does, like touching the fingerprint sensor would lead to immediate lock screens (could be fixed when deleted the fpc1020.kl file in vendor), and failing to read an adaptive Type C headphones bugs, hope they could be fixed later.
Touch2Fin said:
Hi there, just tried this new ROM and it is pretty nice that most functions are working well, really appreciate your maintainance!
However, this ROM has the same bugs as the previous AICP one does, like touching the fingerprint sensor would lead to immediate lock screens (could be fixed when deleted the fpc1020.kl file in vendor), and failing to read an adaptive Type C headphones bugs, hope they could be fixed later.
Click to expand...
Click to collapse
Yes, it does as it's based on the same trees
Also don't report the fact that pressing the fp will lock the screen as a bug, it's an intended feature, what's not intended is the fact that for some reason it can't be disabled right now
- Is there a minimum firmware base requirement?
- Which GSI variant is supported?
VR25 said:
- Is there a minimum firmware base requirement?
- Which GSI variant is supported?
Click to expand...
Click to collapse
- MB; yes there is, it's just the latest Oreo firmware, on retail channel that would be OPNS27.76-12-22-9
- ARM64 A-Only, given that this device has no A/B support
Also aren't you the guy that made acc?
marcost22 said:
- MB; yes there is, it's just the latest Oreo firmware, on retail channel that would be OPNS27.76-12-22-9
- ARM64 A-Only, given that this device has no A/B support
Also aren't you the guy that made acc?
Click to expand...
Click to collapse
As expected, thanks. This treble implementation is such a gem!
Yes, I'm the acc guy.
Which gapp i should download.. there are 6 files.. i have already tried 3 file form given link..but everytimes showing error.. plz mentioned the perticular download link of gapp
@marcost22 million of thanks to you, never thought will see a official lineage os for moto z play. Its based on 64 bit ?
I would like to say "YOU ARE THE BEST" !!
Subu1990 said:
Which gapp i should download.. there are 6 files.. i have already tried 3 file form given link..but everytimes showing error.. plz mentioned the perticular download link of gapp
Click to expand...
Click to collapse
MindTheGapps-11.0.0-arm64-20220217_100228.zip this one will work !!
VR25 said:
As expected, thanks. This treble implementation is such a gem!
Yes, I'm the acc guy.
Click to expand...
Click to collapse
Thanks!
Also funny finding you here
Subu1990 said:
Which gapp i should download.. there are 6 files.. i have already tried 3 file form given link..but everytimes showing error.. plz mentioned the perticular download link of gapp
Click to expand...
Click to collapse
MindTheGapps-11.0.0-arm64-20220217_100228.zip | by Alessandro Astone for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Also you are expected that if you are able to install a rom, you are able to do a little googling and reading
bunt009 said:
@marcost22 million of thanks to you, never thought will see a official lineage os for moto z play. Its based on 64 bit ?
I would like to say "YOU ARE THE BEST" !!
Click to expand...
Click to collapse
Yes, as all my roms it is a 64bits rom
marcost22 said:
Thanks!
Also funny finding you here
Click to expand...
Click to collapse
I also find funny the fact that you opened this thread just two days before my Z Play got out of the repair store. Nice timing!
Sorry if it's bothering you, when you apply the ROM the front flash is on directly. Did I do something wrong?
Nelsobrinho said:
Sorry if it's bothering you, when you apply the ROM the front flash is on directly. Did I do something wrong?
Click to expand...
Click to collapse
The front flash is on all the time? That's odd
Care to get me a logcat of it? Also, what fw version you were running before
marcost22 said:
The front flash is on all the time? That's odd
Care to get me a logcat of it? Also, what fw version you were running before
Click to expand...
Click to collapse
Sorry friend I posted here but I got very impatient and re-applied the rom and the front flash is ok. The only downside is that NFC is not working in practice, despite being available in the settings menu. Does anyone know or have the same bug?
Nelsobrinho said:
Sorry friend I posted here but I got very impatient and re-applied the rom and the front flash is ok. The only downside is that NFC is not working in practice, despite being available in the settings menu. Does anyone know or have the same bug?
Click to expand...
Click to collapse
Do you by any chance have the chinese (XT1653-03) variant? If not, can you grab me a logcat of the behaviour so i can check it?
Nelsobrinho said:
Sorry friend I posted here but I got very impatient and re-applied the rom and the front flash is ok. The only downside is that NFC is not working in practice, despite being available in the settings menu. Does anyone know or have the same bug?
Click to expand...
Click to collapse
First, thank you very much for the ROM @marcost22
I think it's amazing to bring an "updated" android to an old smartphone
Here I had the same problem with NFC (my variant is XT1635-03)
How I "solved":
restart in twrp (use latest that can mount vendor folder)
mount the vendor partition
Go to /vendor/etc folder
delete the file libnfc-nxp.conf
rename the file libnfc-nxp_retcn.conf to libnfc-nxp.conf
If you have magisk, it won't work.
You have to do this configuration before installing magisk.
joaoantonioe said:
First, thank you very much for the ROM @marcost22
I think it's amazing to bring an "updated" android to an old smartphone
Here I had the same problem with NFC (my variant is XT1653-03)
How I "solved":
restart in twrp (use latest that can mount vendor folder)
mount the vendor partition
Go to /vendor/etc folder
delete the file libnfc-nxp.conf
rename the file libnfc-nxp_retcn.conf to libnfc-nxp.conf
If you have magisk, it won't work.
You have to do this configuration before installing magisk.
Click to expand...
Click to collapse
That retcn file is there for this purpose, but it should be getting done automatically on boot. I'll have to redo this some other time
marcost22 said:
That retcn file is there for this purpose, but it should be getting done automatically on boot. I'll have to redo this some other time
Click to expand...
Click to collapse
"delete the file libnfc-nxp.conf
rename the file libnfc-nxp_retcn.conf to libnfc-nxp.conf"
I redid the whole process but when I get to this part when I delete and rename the file I restart the system and NFC is already disabled even without installing Magisk. I still don't have NFC
Nelsobrinho said:
"delete the file libnfc-nxp.conf
rename the file libnfc-nxp_retcn.conf to libnfc-nxp.conf"
I redid the whole process but when I get to this part when I delete and rename the file I restart the system and NFC is already disabled even without installing Magisk. I still don't have NFC
Click to expand...
Click to collapse
What is your variant?
My variant is XT1653-02
Hello everyone!
I got this device last year and always wanted GSI to run properly in the device. In other guide shows GSI can be properly installed however, it rendered wrong rotation and sound sometimes muffled. I want to get rid ZUI 12/13 because notification problem and suspicious with Chinese rom. With GSI we can have long term device support and security. I am using stock recovery only and stock fastbootd. Root with magisk is sometime hit or miss. I managed to fix with a ported miui vendor img and simple build.prop alteration.
Prepare:
Working device
Unlocked bootloader
Win7/8/10/11 (installed FastBoot driver)
Make sure to be based on the ZUI_13.0.430 version (link attached)
Download GSI J716F script.
Type C dongle to mouse. (needed)
Steps:
1) Restore with Qfil to ZUI_13.0.430 (link attached)
2) Download and extract GSI J716F script.
3) Reboot your device to fastbootd with adb reboot fastboot.
4) Run gsi system flasher for j716f only.exe and press 1. On next screen, press any button. Connect your device until it restore.
5) Do factory reset in recovery mode then reboot.
6) Once system is rebooted. Connect type C dongle with mouse to the device and finish the setup. Please note that rotation and touch is not in sync.
7) Install magisk and make sure proper root. Install build.prop editor. (link attached)
8) Open build.prop and grant superuser access. Add entry ro.surface_flinger.primary_display_orientation at first column and ORIENTATION_270 at second column.
8. Save dan reboot.
9. Everything is working now but bare in mind you need to install some magisk module to get proper sound manager, safetynet fix, AOD support and auto brightness fix from Y700.
What is wroking:
1. Wifi
2. Bluetooth
3. Brightness adjustment (Auto brightness need magisk module)
4. 60Hz/90Hz refresh rate
5. Camera, flashlight and face unlock
6. Working sensors
7. Screen rotation
8. Dual speakers
9. Linear motor
Bug: d2tw and flip screen
Please tell me other bugs
Download : https://drive.google.com/drive/folders/1F4oQflyK6PgfnstJacFOPGaQzZMmJyfQ?usp=sharing
Once root and magisk is properly installed. You can install several magisk module to fix, play store verfication, auto brightness, sound manager and APTX (HD) module for bluetooth.
1) Install each modules.
2) Reboot.
Install these 2 apk to get better camera and proper AOD support
1) Install trebleApp(1).apk
2) Gcam MGC_8.1.101_A9_GV2b_snap.apk
3) You can disable the stock camera app.
In case you want to try other gsi system instead of CrDroid 8.6 prepped. You can simply replace system.img in gsi j716f scipt.zip\gsi j716f scipt\bin\system\system.img.
See the difference.
Reserved
is L1 working?
lordzinh said:
is L1 working?
Click to expand...
Click to collapse
Nope.
Thanks for this...
I hate ZUI, been wanting to try GSI for a while, just didn't want the bugs...
This looks like it's mostly working now .
gunalarix8 said:
lease tell me other bugs
Download : https://drive.google.com/drive/folders/1F4oQflyK6PgfnstJacFOPGaQzZMmJyfQ?usp=sharing
Click to expand...
Click to collapse
Some files on the "3 Tools folder have 0 bytes size" could you reupload them
{
"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"
}
Please remove double post
Awesome work, thanks so much. Hoping to try this soon, how's the battery life been though compared to stock?
eDooM85 said:
Some files on the "3 Tools folder have 0 bytes size" could you reupload themView attachment 5730137
Click to expand...
Click to collapse
sorry for late reply, files has been updated. thank you
gunalarix8 said:
sorry for late reply, files has been updated. thank you
Click to expand...
Click to collapse
Thx I'll try to install a GSI this weekend.
I have been waiting for this, looks like it is mostly working. saw the video too.
thank you for doing this. I will try this because I hate ZUI
gunalarix8 said:
lease tell me other bugs
Click to expand...
Click to collapse
Just installed it, Look good so far just a couple of question:
How did you enable Linux SE?
also how do you customiz/disable this bar?
eDooM85 said:
Just installed it, Look good so far just a couple of question:
How did you enable Linux SE?
View attachment 5736353
also how do you customiz/disable this bar?
View attachment 5736359
Click to expand...
Click to collapse
We cannot enable selinux, however we can disable the notification in security.
I dont know how to customize the naz bar.
How is the system? Fully working now?
gunalarix8 said:
We cannot enable selinux, however we can disable the notification in security.
I dont know how to customize the naz bar.
How is the system? Fully working now?
Click to expand...
Click to collapse
the only thing complicated is the setting up part without touch control (my mouse was also detected as a keyboard) and pretty much I had to config without conecting to the internet (couldnt enter my wifi password),
but after the "build.prop" step, everything else is working fine so far
gunalarix8 said:
We cannot enable selinux, however we can disable the notification in security.
I dont know how to customize the naz bar.
How is the system? Fully working now?
Click to expand...
Click to collapse
Just an update, streaming apps just give errors, I tried Disney+/HBO Max/Paramount only youtube works fine, that's a deal breaker for me , I will try other GSI
eDooM85 said:
Just an update, streaming apps just give errors, I tried Disney+/HBO Max/Paramount only youtube works fine, that's a deal breaker for me , I will try other GSI
Click to expand...
Click to collapse
Isn't that because the widevine level (DRM) is wrong due to the unlocked bootloader?
I think all GSI roms will suffer the same problem... unless someone knows how to fix it with a magisk module or something ... as I they all need an unlocked bootloader..
Other than the DRM issue how does itbrun?
tinybilbo said:
Isn't that because the widevine level (DRM) is wrong due to the unlocked bootloader?
I think all GSI roms will suffer the same problem... unless someone knows how to fix it with a magisk module or something ... as I they all need an unlocked bootloader..
Other than the DRM issue how does itbrun?
Click to expand...
Click to collapse
The problem it's not widevine Lv1 with Lv3 you can view content, the diference is that you can see it only in SD (480p) right now just throws an error loading content for example disney+ show this:
Do you know if OTA updates will work with this method? Or would you have to manually set everything up again.
gunalarix8 said:
With GSI we can have long term device support and security.
Click to expand...
Click to collapse
You say you care about security but you're okay with selinux in permissive mode?
I have just tried this but I'm not convinced this is a secure rom. Theres this chinese app that randomly appeared and dissapeared. It's called com.iflytek.inputmethod and is made by iFlytek, a chinese state owned company which has been sanctioned by the US for spying.
I'm reverting to another GSI without autorotate.