Database Info

Redmi Note 5 HDR+ Samples and magisk methods to enable Camera2 API

Original post with samples photos [link]
{
"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"
}
Here are the full photos in this album.
Before using the Google Camera HDR+, you have to enable Camera API 2 in the MIUI, unless any version of Google Camera you install WILL HAVE NO HDR+ EFFECT OR CRASH AFTER OPENING!!!
The way I choose to enable Camera 2 API on MIUI is through the Magisk platform, and there are 4 steps of prerequisites to get to this:
Unlock the bootloader
You need to go to MIUI unlock page and follow the steps to unlock your phone’s Bootloader.
During the process, you will also need to install the driver in computer for your phone.
Flash the 3'rd party recovery, like TWRP
Go to TWRP devices page to download the TWRP recovery for your model, and boot your phone into Fastboot Mode by holding the volume down & power button until it boot into fastboot.
Also download the Android platform tools, unzip, and open CMD on windows or terminal on macOS and cd (move) to your unzip directory.
After that, flash the TWRP recovery into your phone.
Code:
fastboot flash recovery $your_download_recovery.img
Check to flash process is success (you will see the “OK” in the command line), and boot your phone into recovery:
Code:
fastboot boot $your_download_recovery.img
and slide the button to right to enable modification, disable the MIUI’s recovery.
Flash the Magisk platform
Now the custom 3'rd part recovery is completely installed, we can install Magisk now.
Download the magisk from the developer’s XDA page, copy into your phone SD, select and slide to flash the magisk with TWRP install function .
Flash the Camera 2 API enabler
The previous Camera 2 API enabler is decrepit, so I rewrite a newer version that can work with Magisk 15+.
Flash the zip to enable enable Camera 2 API.
You can check whether you successfully enable the Camera 2 API by Camera 2 API probe:
Install Google Camera Port (HDR+) App
Now the prerequisite is complete, we can finally install the Google Camera Port now.
Here is a Port Google Camera collection page, I recommend using MGCamera_5.1.0.18_R4X series which maintain by @Arthur, and here is my recommend settings:

[Reserved]

Are you using China veriant or Indian?

Shahitto said:
Are you using China veriant or Indian?
Click to expand...
Click to collapse
I bought it at Taiwan, it's a China Variant which use Global Android 8.1 MIUI 9.5 ROM

jhangyu said:
I bought it at Taiwan, it's a China Variant which use Global Android 8.1 MIUI 9.5 ROM
Click to expand...
Click to collapse
So it will also work with indian variant? correct?
Also does this method work with Custom oreo ROM?

KuldeepShivankar said:
So it will also work with indian variant? correct?
Also does this method work with Custom oreo ROM?
Click to expand...
Click to collapse
Yes, this magisk trick can work on any xiaomi device announced in 3 years

Can anybody post front camera megapixel screen? In MIUI 10, my phone front camera megapixel is limited to 5mp.

I followed your settings in Latest RR Rom and mine is China variant but front camera HDR in front portrait doesn't work in low light at all. Thanks for sharing

Can you pls upload thecamera2api enabler here?

It doesn't seems to work for me, I have enabled persist.camera.HAL3.enabled=1 but it still run legacy mode
I'm on Xiaomi Redmi Note Pro (china) running xiaomi.eu rom 8.5.10 with magisk 16.4
any suggestions?

krizky82 said:
It doesn't seems to work for me, I have enabled persist.camera.HAL3.enabled=1 but it still run legacy mode
I'm on Xiaomi Redmi Note Pro (china) running xiaomi.eu rom 8.5.10 with magisk 16.4
any suggestions?
Click to expand...
Click to collapse
I have exactly the same issue. It seems to be a Xiaomi.eu related issue.

n3w0rk said:
I have exactly the same issue. It seems to be a Xiaomi.eu related issue.
Click to expand...
Click to collapse
thanks for the confirmation... I guess I'll try it later when MIUI 10 came out, I hope it will be fixed by then.

how do i download the zip from github? is it just the green clone or download? tried it transfered the zip and flashed through twrp, got a error in return
EDIT: got it working by unzipping and rezipping just the files then flashing it.

can the zip be used on Nougat 9.2 version?

krizky82 said:
It doesn't seems to work for me, I have enabled persist.camera.HAL3.enabled=1 but it still run legacy mode
I'm on Xiaomi Redmi Note Pro (china) running xiaomi.eu rom 8.5.10 with magisk 16.4
any suggestions?
Click to expand...
Click to collapse
Please read the article again, I use a MAGISK MODULE to enable camera2 api, not modify the .prop file.

puttytatko said:
Can you pls upload thecamera2api enabler here?
Click to expand...
Click to collapse
No, please just download it from github.

I tried many Magisk module and non of them is working. The Module is executed successfully, but camera2api can't be activated.
The only method for me to active camera2api is to edit the build.prop.
Weird...
I'm using MIUI 9.5.6.0

e_mc_square said:
I tried many Magisk module and non of them is working. The Module is executed successfully, but camera2api can't be activated.
The only method for me to active camera2api is to edit the build.prop.
Weird...
I'm using MIUI 9.5.6.0
Click to expand...
Click to collapse
Same here.

jhangyu said:
Please read the article again, I use a MAGISK MODULE to enable camera2 api, not modify the .prop file.
Click to expand...
Click to collapse
I use magisk too

jon_snowGOT said:
Same here.
Click to expand...
Click to collapse
It happen on global stable rom.

Dolby Atmos™ for OOS - Closed

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

Nexus 6P - Lineage OS 15.1 - Magisk fails CTS Profile check

Hi,
I'm trying to install a custom rom (Lineage OS 15.1), and gain super user access without failing the safetynet checks.
I have TWRP as my recovery and I was able to sideload the LineageOS and GApps and Magisk without a problem (with clearing caches).
I installed the latest magisk version (23.0) - I enabled MagiskHide, and hid the name of the magisk package (I forgot the name of the option, but now it says "restore the magisk app").
I also tried installing the Magisk Hide Props config module.
Once I managed to gain root access without tripping the safetynet checks through a combination of Magisk, Smali patcher and App Systemizer module (I was running android 8.0 version at that time) - however I do not remember the process and cannot find the thread again.
One thing I noted was that magisk still says install (even tho it says installed), see below image for details.
When iImanaged to run this process on stock android 8.0, I remember that these options where ticked and green (installing magisk and app)
I do have root access and am able to install apps as system and etc. The safety net checks are what I'm missing.
Does anyone have any idea what am I missing? Any help would be really appreciated.
{
"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"
}

StyleM said:
Hi,
I'm trying to install a custom rom (Lineage OS 15.1), and gain super user access without failing the safetynet checks.
I have TWRP as my recovery and I was able to sideload the LineageOS and GApps and Magisk without a problem (with clearing caches).
I installed the latest magisk version (23.0) - I enabled MagiskHide, and hid the name of the magisk package (I forgot the name of the option, but now it says "restore the magisk app").
I also tried installing the Magisk Hide Props config module.
Once I managed to gain root access without tripping the safetynet checks through a combination of Magisk, Smali patcher and App Systemizer module (I was running android 8.0 version at that time) - however I do not remember the process and cannot find the thread again.
One thing I noted was that magisk still says install (even tho it says installed), see below image for details.
When iImanaged to run this process on stock android 8.0, I remember that these options where ticked and green (installing magisk and app)
I do have root access and am able to install apps as system and etc. The safety net checks are what I'm missing.
Does anyone have any idea what am I missing? Any help would be really appreciated.
View attachment 5324283View attachment 5324285View attachment 5324287
Click to expand...
Click to collapse
try using magisk 20.4 n dont update just keep the 20.4 version

howdeedodat said:
try using magisk 20.4 n dont update just keep the 20.4 version
Click to expand...
Click to collapse
Hey man thanks for the tip. I first wiped data, cache, dalvik and system, then flashed lineageos 15.1 with magisk 20.4 and gapps. I setup magiskhide and changed the package name. I also installed the magisk hide props. What am i missing
I noticed on a forum somewhere that for magisk hide module you're supposed to open a terminal and run props command... What do you do from there? I'm so confused, i have no clue whats wrong.
Fyi the error is still the same see below images.
One thing i did differently now was that i didnt reflash stock first (just flashed lineage magisk and gapps after wiping)... Do you think it makes a difference?
I'll give it a try tomorrow as i was in a rush.

StyleM said:
Hey man thanks for the tip. I first wiped data, cache, dalvik and system, then flashed lineageos 15.1 with magisk 20.4 and gapps. I setup magiskhide and changed the package name. I also installed the magisk hide props. What am i missing
I noticed on a forum somewhere that for magisk hide module you're supposed to open a terminal and run props command... What do you do from there? I'm so confused, i have no clue whats wrong.
Fyi the error is still the same see below images.
One thing i did differently now was that i didnt reflash stock first (just flashed lineage magisk and gapps after wiping)... Do you think it makes a difference?
I'll give it a try tomorrow as i was in a rush.
Click to expand...
Click to collapse
the 5th picture which is show the emulator function, it will help u to change device fingerprint, just make sure u found the correct one for ur phone n u will be totally succesfull passing the safety net, but before u do that might be this thread could fix ur safety net without using the terminal emulator ?

howdeedodat said:
the 5th picture which is show the emulator function, it will help u to change device fingerprint, just make sure u found the correct one for ur phone n u will be totally succesfull passing the safety net, but before u do that might be this thread could fix ur safety net without using the terminal emulator ?
Click to expand...
Click to collapse
Do i need to sideload this on the rom, or is it a magisk module (magisk didnt like thst zip tile)

StyleM said:
Do i need to sideload this on the rom, or is it a magisk module (magisk didnt like thst zip tile)
Click to expand...
Click to collapse
flash it in magisk or sideload theres no different as long u have tha magisk on ur phone because its a magisk module

General [GSI] Crdroid 8.6 For J716F

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.

Question [SOLVED] Revanced working?

Did anyone try installing revanced manager on the P7P? Get it working?
I installed the manager and it doesn't seem to see when I patch the youtube apk. It goes through the process of patching the youtube apk. I installed using non-root methods and when I try to open the newly installed apk that revanced patches, it just sits on a black screen.
When I tried installing with the root method, the apk is not visible in the app drawer.
EDIT: Confirmed working, many different ways... Revanced builder using Windows, revanced builder using android, rooted and non-rooted. Rooted using revanced manager. Rooted using magisk module.

I didn't use the manager, I used the builder and that was fine.

Do you have a link to the builder and method you used?
Did you use the android phone method or windows injection method of builder?

EtherealRemnant said:
I didn't use the manager, I used the builder and that was fine.
Click to expand...
Click to collapse
I think I found my problem. When using the revanced manager, they don't recommend using dpi related apks or split apks but installing a no dpi apk instead. If you do, they say it causes issues of not loading.

rester555 said:
Do you have a link to the builder and method you used?
Did you use the android phone method or windows injection method of builder?
Click to expand...
Click to collapse
I used this one.
GitHub - reisxd/revanced-builder: A NodeJS ReVanced builder
A NodeJS ReVanced builder. Contribute to reisxd/revanced-builder development by creating an account on GitHub.
github.com
Did it in Windows.
When selecting the YouTube version to use, I scrolled until the first recommended one.

CONFIRMED working with vanced manager, root method with youtube 17.36.37 no dpi version downloaded from 3rd party site.
When using microg non-root method, the apk patched goes to a black screen.

rester555 said:
CONFIRMED working with vanced manager, root method with youtube 17.36.37 no dpi version downloaded from 3rd party site.
When using microg non-root method, the apk patched goes to a black screen.
Click to expand...
Click to collapse
Weird. I am not rooted. Guess the builder just works better.

EtherealRemnant said:
Weird. I am not rooted. Guess the builder just works better.
Click to expand...
Click to collapse
Agreed, they have been working on the builder much longer than the manager.
And if memory serves me, the windows version doesn't require micro g to install it on the phone. Is that correct or do you need it?

rester555 said:
Agreed, they have been working on the builder much longer than the manager.
And if memory serves me, the windows version doesn't require micro g to install it on the phone. Is that correct or do you need it?
Click to expand...
Click to collapse
I built it with micro G because it said to but I don't know if it was necessary or not.

I use the nice and easy magisk module:
GitHub - j-hc/revanced-magisk-module: Extensive ReVanced builder. Builds both modules and APKs. Updated daily.
Extensive ReVanced builder. Builds both modules and APKs. Updated daily. - GitHub - j-hc/revanced-magisk-module: Extensive ReVanced builder. Builds both modules and APKs. Updated daily.
github.com

Didn't realize there was one! Thanks!

Works for me using revanced manager non root

I saw this and was trying to use the builder because it looks like one of the options is to detach the app from the market so it's not constantly updating and needing redone. I've tried several times and keep getting this below. Any ideas what I'm doing wrong?
[builder] org.jf.dexlib2.dexbacked.DexBackedDexFile$NotADexFile: Not a valid dex magic value: ef bb bf 3c 3f 78 6d 6c at org.jf.dexlib2.util.DexUtil.verifyDexHeader(DexUtil.java:93) at lanchon.multidexlib2.RawDexIO.readRawDexFile(RawDexIO.java:53) at lanchon.multidexlib2.RawDexIO.readRawDexFile(RawDexIO.java:43) at lanchon.multidexlib2.MultiDexIO.readMultiDexContainer(MultiDexIO.java:66) at lanchon.multidexlib2.MultiDexIO.readMultiDexContainer(MultiDexIO.java:51) at lanchon.multidexlib2.MultiDexIO.readMultiDexContainer(MultiDexIO.java:42) at lanchon.multidexlib2.MultiDexIO.readDexFile(MultiDexIO.java:36) at app.revanced.patcher.Patcher.addFiles(Patcher.kt:80) at app.revanced.patcher.Patcher.addFiles$default(Patcher.kt:72) at app.revanced.utils.patcher.PatcherKt.mergeFiles(Patcher.kt:80) at app.revanced.cli.patcher.Patcher.start$revanced_cli(Patcher.kt:23) at app.revanced.cli.command.MainCommand.run(MainCommand.kt:157) at picocli.CommandLine.executeUserObject(CommandLine.java:1939) at picocli.CommandLine.access$1300(CommandLine.java:145) at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2358) at picocli.CommandLine$RunLast.handle(CommandLine.java:2352) at picocli.CommandLine$RunLast.handle(CommandLine.java:2314) at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2179) at picocli.CommandLine$RunLast.execute(CommandLine.java:2316) at picocli.CommandLine.execute(CommandLine.java:2078) at app.revanced.cli.main.MainKt.main(Main.kt:7)

I'm having problems with this using revanced manager. patches ok and installs ok (root), works fine for a bit, then starts to crash on start. any clues?
magisk module seems to work but includes the "theme" patch which gives it a black theme rather than dark.
edit: also tried non root method with micro g but chromecast doesn't work. I'm stuck.

whatsisnametake2 said:
I'm having problems with this using revanced manager. patches ok and installs ok (root), works fine for a bit, then starts to crash on start. any clues?
magisk module seems to work but includes the "theme" patch which gives it a black theme rather than dark.
edit: also tried non root method with micro g but chromecast doesn't work. I'm stuck.
Click to expand...
Click to collapse
Download the non dpi version of the app. Don't get the multi APK version.

just for anyone else following this later, I sorted this out. I actually have youtube premiere because it's the only way to have no adverts on the chromecast. so I think some of the no advert patches might have been conflicting. so I just applied the bare minimum patches I wanted, swipe gestures sponsor block and remember resolution, after that it was fine.

I fixed the problem in root version
1/ install ur patch (as root, so u don't need to allow microg )
2/ install as root (close the app without oppening youtube)
3/ go to magisk and configure deny list
4/ do like that in pic and restart ur device
5/ run youtube without any problem
{
"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"
}

Ahsene said:
I fixed the problem in root version
1/ install ur patch (as root, so u don't need to allow microg )
2/ install as root (close the app without oppening youtube)
3/ go to magisk and configure deny list
4/ do like that in pic and restart ur device
5/ run youtube without any problem
View attachment 5759687
Click to expand...
Click to collapse
How are you dealing with the update blockign so far? I have tryed Update Locker, but it seems that it still updates the app and ads reapper.