How To Guide [Root] Xiaomi 12S Ultra Netflix L1 FHD HDR10 Tweak - Xiaomi 12S Ultra

ok, so I finally figured out how to do this all.
sorry the screen shots are in Korean, I'm too lazy to go back and change the language but you can still see the important stuff,
like the device name, DRM L1, resolution FHD, and HDR 10 support.
{
"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"
}
Basically, you add build prop value so that the netflix would use L1 instead of L3,
then you spoof the device to pixel 6 pro to deal with 12s ultra not being officially supported by netflix (which requires to use hdr)
MagiskHide Props
LSposed Zygisk
Termux
Pixelify Google Photo
These are what you need, install magiskhide pros and lsposed module on magisk, then reboot the device.
Use termux to type in following commands,
su
props
5
n
ro.netflix.bsp_rev
Q8450-34634-1
you are basically getting super user permission, launch MagiskHide Props menu,
5 for add/edit custom build.prop, n for new,
then name and value for the entry we need.
Once it is done, it will ask you to reboot, so reboot the device.
Then, go to lsposed, enable Pixelify GPhotos module, and check netflix app.
Remove all data on your netflix app, then log back in to your accont.
Now you should see your device spoofed as Pixel 6 pro using 12S Ultra's L1 DRM,
giving all what you need
@BlackSoulxxx
Big shoutout to blacksoul for providing build.prop value, it was a great shortcut from there to figure out how to set up.

Nabicook said:
ok, so I finally figured out how to do this all.
sorry the screen shots are in Korean, I'm too lazy to go back and change the language but you can still see the important stuff,
like the device name, DRM L1, resolution FHD, and HDR 10 support.
View attachment 5686065
Basically, you add build prop value so that the netflix would use L1 instead of L3,
then you spoof the device to pixel 6 pro to deal with 12s ultra not being officially supported by netflix (which requires to use hdr)
MagiskHide Props
LSposed Zygisk
Termux
Pixelify Google Photo
These are what you need, install magiskhide pros and lsposed module on magisk, then reboot the device.
Use termux to type in following commands,
su
props
5
n
ro.netflix.bsp_rev
Q8450-34634-1
you are basically getting super user permission, launch MagiskHide Props menu,
5 for add/edit custom build.prop, n for new,
then name and value for the entry we need.
Once it is done, it will ask you to reboot, so reboot the device.
Then, go to lsposed, enable Pixelify GPhotos module, and check netflix app.
Remove all data on your netflix app, then log back in to your accont.
Now you should see your device spoofed as Pixel 6 pro using 12S Ultra's L1 DRM,
giving all what you need
@BlackSoulxxx
Big shoutout to blacksoul for providing build.prop value, it was a great shortcut from there to figure out how to set up.
Click to expand...
Click to collapse
Thanks buddy
If the netflix app updates, will it keep the settings?
Ian

Quick question , These are what you need, install magiskhide pros and lsposed module on magisk, then reboot the device.
Found it but do i need to root my device ?

mritl said:
Quick question , These are what you need, install magiskhide pros and lsposed module on magisk, then reboot the device.
Found it but do i need to root my device ?
Click to expand...
Click to collapse
yes. these are magisk modules, meaning that you have to root

I'm using Dev ROM now, it started to support full HD in NF. And I heard xiaomi will officially support this next month. Let's just wait for new system update.

Thanks for update. Do you get hdr

ninja003 said:
I'm using Dev ROM now, it started to support full HD in NF. And I heard xiaomi will officially support this next month. Let's just wait for new system update.
Click to expand...
Click to collapse
thanks for the info!

Unfortunately even with the fix we still cant use the Dolby Vision and Dolby Atmos in Netflix as the firmware is buggy. On Xiaomi 12 -> 12S Pro we can stream Dolby contents but not on this phone. Peoples, please use the Feedback app to tell Xiaomi they need to fix this issue.

BlackSoulxxx said:
Unfortunately even with the fix we still cant use the Dolby Vision and Dolby Atmos in Netflix as the firmware is buggy. On Xiaomi 12 -> 12S Pro we can stream Dolby contents but not on this phone. Peoples, please use the Feedback app to tell Xiaomi they need to fix this issue.
Click to expand...
Click to collapse
Hi Friend
Problem is that this phone is supported in China only as its only out there. Means its for Chinese users to report issue but am sure in china they are using a different stream service and not so much Netflix. I think Xioami will release an update so HD will work but HDR options wont come as its not a global release.

ninja003 said:
I'm using Dev ROM now, it started to support full HD in NF. And I heard xiaomi will officially support this next month. Let's just wait for new system update.
Click to expand...
Click to collapse
Hey can you give me a link to the newest dev Rom?

Hello, i did all your steps but i only get l1 but no HDR Support. After your steps i did another one. I installed this unlocker https://github.com/akirasup3r/unlocker und choosed number 1 and after this i have got HDR Support.
Nabicook said:
ok, so I finally figured out how to do this all.
sorry the screen shots are in Korean, I'm too lazy to go back and change the language but you can still see the important stuff,
like the device name, DRM L1, resolution FHD, and HDR 10 support.
View attachment 5686065
Basically, you add build prop value so that the netflix would use L1 instead of L3,
then you spoof the device to pixel 6 pro to deal with 12s ultra not being officially supported by netflix (which requires to use hdr)
Click to expand...
Click to collapse
Nabicook said:
MagiskHide Props
LSposed Zygisk
Termux
Pixelify Google Photo
These are what you need, install magiskhide pros and lsposed module on magisk, then reboot the device.
Use termux to type in following commands,
su
props
5
n
ro.netflix.bsp_rev
Q8450-34634-1
you are basically getting super user permission, launch MagiskHide Props menu,
5 for add/edit custom build.prop, n for new,
then name and value for the entry we need.
Once it is done, it will ask you to reboot, so reboot the device.
Then, go to lsposed, enable Pixelify GPhotos module, and check netflix app.
Remove all data on your netflix app, then log back in to your accont.
Now you should see your device spoofed as Pixel 6 pro using 12S Ultra's L1 DRM,
giving all what you need
@BlackSoulxxx
Big shoutout to blacksoul for providing build.prop value, it was a great shortcut from there to figure out how to set up.
Click to expand...
Click to collapse
,

thank for your sharing. now i can get l1,but with out hdr,am i missing something?what should i do

Connally_z said:
thank for your sharing. now i can get l1,but with out hdr,am i missing something?what should i doView attachment 5705175
Click to expand...
Click to collapse
Do my steps i write above your tweet and you should get hdr.

energykriger said:
Do my steps i write above your tweet and you should get hdr.
Click to expand...
Click to collapse
i had been followed your steps and it's l1 now,but no hdr

But you need to follow the steps of the owner of this thread to.

I think i found another way.Maybe is easier.Install the file below on magisk,it will pertend your phone to mi11 ultra.And them you can get 1080p and hdr10.Someone tell me they can get dolby vison and dolby atmos.

it work

I found a New Way. Update to 13.0.9, attention you must install the official twrp, unofficial dont work for me. Than you have l1 support, but no HDR. Than install the unlocker, choose number 1 and you have HDR support with dolby vision. You dont need anymore to spoof your device to another one.

energykriger said:
I found a New Way. Update to 13.0.9, attention you must install the official twrp, unofficial dont work for me. Than you have l1 support, but no HDR. Than install the unlocker, choose number 1 and you have HDR support with dolby vision. You dont need anymore to spoof your device to another one.
Click to expand...
Click to collapse
what is unlocker ? are you using original rom or eu rom ?

EU Rom. This unlocker. https://github.com/akirasup3r/unlocker/releases/tag/p4 . After that everything works.

Related

[Magisk] Rayglobe Module

{
"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"
}
Hello Xda Users,
This is first magisk module for our razer. It will install stuff that you can see in features section. Only requirement is that you need Magisk and obviously TWRP. As this is magisk module you don't need to worry about system space. Magisk will install app to magisk.img which is mounted in your data partition... This is magic of MAGISK....!
Requirement:
Magisk v15.1 - Root & Universal Systemless Interface [
Procedure:
1. Download magisk_rayglobe_os.zip
2. Goto Magisk Manager > modules > add module > select "magisk_rayglobe_os.zip" using file manager
3. Reboot device.
4. Enjoy systemless Rayglobe world... Happy flashing ...!
Uninstall:
To remove this module simply goto Magisk Manager > modules and delete "magisk_rayglobe_os.zip".
Download:
- Android File Host
Click Me for Changelog:
(Note: Before updating this MOD to new version PLEASE uninstall the previous version (check Uninstall: ) and then install NEW one.)
(Note: Download according to your Magisk version. USE latest Magisk.......)
Features
- Build.prop stuff for volume and more audio steps
- Themed youtube
- Service.jar hacked to delete sign
- Framework-res adjustement to ambient light and dim
- New Miracast flash in settings/video
- AptxHd driver
- IOS 11 emoji
Credits:
@topjohnwu for Magisk and Modules
@Team Bad Boyz for rebooter apk
@KevinnX8 Youtube
@github - link for more information
If I forgot someone please write me in PM and I'll update this section
Reserved
Awesome! Thanks for your work.. We need lots more of these little tweaks and stuff. I'm waiting for center clock with small date and am/pm from roms... Probably #2 thing I miss besides custom kernels.
Keep up the good work!
mikeandjaimie said:
Awesome! Thanks for your work.. We need lots more of these little tweaks and stuff. I'm waiting for center clock with small date and am/pm from roms... Probably #2 thing I miss besides custom kernels.
Keep up the good work!
Click to expand...
Click to collapse
Xposed + Flat Style Bar Indicators
DarkestSpawn said:
Xposed + Flat Style Bar Indicators
Click to expand...
Click to collapse
Ok next version I'll add this.
Blob emoji are the only emoji I want to see. . Thanks for the module.
Anyone get the Google pixel ar stickers working in the camera with this magisk?
https://www.xda-developers.com/enable-google-pixel-ar-stickers-nexus-5x-nexus-6p-oneplus-3-xiaomi-mi-5/
Delete what sign?
Screen mirroring does not works, when you try it it will turn off your phone
mikeandjaimie said:
Awesome! Thanks for your work.. We need lots more of these little tweaks and stuff. I'm waiting for center clock with small date and am/pm from roms... Probably #2 thing I miss besides custom kernels.
Keep up the good work!
Click to expand...
Click to collapse
center clock works with xtended settings app and quite a few others too.xposed needs to be installed first to make it work.this can be done through magisk module downloads
Does anyone have this working for the latest 16.0 magisk? I keep getting an error trying to install it.
sinitik said:
Does anyone have this working for the latest 16.0 magisk? I keep getting an error trying to install it.
Click to expand...
Click to collapse
Yes it's working. Try installing it in recovery.
silvercat said:
Yes it's working. Try installing it in recovery.
Click to expand...
Click to collapse
That's incredibly strange, I tried that prior and then it didn't work. However doing it again later it installed flawlessly. Thank you though.
Any preview screenshots?
Module is awesome, but I can't seem to get aptx working On 8.1 Oreo. I have an aptx headset that I have used with other phones that support aptx for a while, not sure if you can fix this bit would be appreciated.. I'll buy you a beer on payday or something if you can @raimondomartire
Any update @raimondomartire?
It seems that my build.prop is read only, and even magisk modules can't modify it (though other modules like viper are working) - not sure if that helps!
manor7777 said:
I can't seem to get aptx working On 8.1 Oreo
Click to expand...
Click to collapse
I see in developer options there's a Bluetooth codec option that lets you select apt x and apt x hd. Have you set it there and it still doesn't work?
Munk0 said:
I see in developer options there's a Bluetooth codec option that lets you select apt x and apt x hd. Have you set it there and it still doesn't work?
Click to expand...
Click to collapse
Correct
i get flashing error on latest stock OS oreo 8.1 update running magisk 16.4
how do i load this module @raimondomartire ?
manor7777 said:
Module is awesome, but I can't seem to get aptx working On 8.1 Oreo. I have an aptx headset that I have used with other phones that support aptx for a while, not sure if you can fix this bit would be appreciated.. I'll buy you a beer on payday or something if you can @raimondomartire
Click to expand...
Click to collapse
this is not something you can select as you please. aptx will automatically activate when connected to a device that prefers/supports it. if you are connected to a device that you KNOW supports aptx and it's not showing aptx when connected to said device, then you might have a problem.

Passing SafetyNet and using tez on whyred

{
"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"
}
If you are getting a CTS profile mismatch like shown above then this guide will be able to help you.
Note:
This guide will only help if you have some build prop unsafe value. If due to some x,y, reason magisk hide is not working on your rom then this guide won't be able to help. as this is the case with quite a few rom on whyred at the moment. This will soon change with time. This guide is most suitable for leaked MIUI builds, dev and beta MIUI roms, and few custom ROMs.
Step 1:
Open magisk manager.
Download and install magisikhide props Module ( XDA thread )
Screenshot below
Step 2:
Download any terminal app. recommended http:whyred.tk/terminal
Open terminal app
type "su" and give it root permission
type "props" to launch magiskhide props module interface
Screenshot below
Step 3:
Choose 1st option
Screenshot below
Step 4:
Read this before proceeding further.
Now you could either try the fingerprint which is already included in the module. I submitted the fingerprint for whyred in the database. it works for most ROM and was working at that time. It still works. So just type "f" then select "xiaomi" and choose "whyred" . set that fingerprint and reboot. Or you can get fingerprint from someone who is on latest stable ROM. will add the procedure to gather fingering at the end.
will also include bunch of fingerprint of whyred from various ROM that passes safety net. so you can try them all and see which one is working for your current ROM.
copy paste this fingerprint in terminal and hit enter
xiaomi/whyred/whyred:8.1.0/OPM1.171019.011/V9.5.12.0.OEICNFA:user/release-keys
Screenshot below
Step 5:
reboot and check for safety net status again, will pass now. if it doesn't then try different fingerprint. if you have tried all fingerprints then something wrong with the ROM that is causing magiskhide not to work properly or there is some prop value that needs to be modified as well. fingerprint is not enough. please visit XDA thread of the module to know more. If you own whyred then you can also discuss about this here.
Screenshot below
Source
magiskhide prop module thread
Working Fingerprints
to submit a working fingerprint please post below . I will add those to the list as well
xiaomi/whyred/whyred:8.1.0/OPM1.171019.011/V9.5.12.0.OEICNFA:user/release-keys
xiaomi/whyred/whyred:8.1.0/OPM1.171019.011/V9.5.6.0.OEIMIFA:user/release-keys
xiaomi/whyred/whyred:7.1.1/NGI77B/V9.2.13.0.NEIMIEK:user/release-keys
Working Fingerprints
to submit a working fingerprint please post below . I will add those to the list as well
xiaomi/whyred/whyred:8.1.0/OPM1.171019.011/V9.5.12.0.OEICNFA:user/release-keys
xiaomi/whyred/whyred:8.1.0/OPM1.171019.011/V9.5.6.0.OEIMIFA:user/release-keys
xiaomi/whyred/whyred:7.1.1/NGI77B/V9.2.13.0.NEIMIEK:user/release-keys
Hi, thanks for this thread.
I tried all three signatures, but didn't pass safetynet.
I'm running 8.5.31
dhirenmathur said:
Hi, thanks for this thread.
I tried all three signatures, but didn't pass safetynet.
I'm running 8.5.31
Click to expand...
Click to collapse
on 8.6.11 its working
devcon69 said:
on 8.6.11 its working
Click to expand...
Click to collapse
In the screenshots, you seem to be running 8.6.6, I tried that too, even tried signatures from different devices, but it doesn't seem to work. I can't seem to figure out why.
I am on RR rom in redmi note 5 pro Indian version. I followed the same steps as said and rebooted the phone and got safetynet check as true for cts profile. So I try to login to tez but it showed error telling that I am running on custom rom. So I checked cts profile, it was still true. But once I rebooted again and checked it was false again
technology-informer said:
I am on RR rom in redmi note 5 pro Indian version. I followed the same steps as said and rebooted the phone and got safetynet check as true for cts profile. So I try to login to tez but it showed error telling that I am running on custom rom. So I checked cts profile, it was still true. But once I rebooted again and checked it was false again
Click to expand...
Click to collapse
This issue is fixed in the latest RR build
technology-informer said:
This issue is fixed in the latest RR build
Click to expand...
Click to collapse
I am on the latest build of RR. But it is not working.
Triggered from RN5pro
dhirenmathur said:
Hi, thanks for this thread.
I tried all three signatures, but didn't pass safetynet.
I'm running 8.5.31
Click to expand...
Click to collapse
Adding more steps. Will do it tomorrow. Also this is for cts profile mismatch. Sometimes magiskhide doesn't work properly on se roms. Last few miui version is having issue. From what i could figure out it might be due te selinux state. Magiskhide is not able to hide that. Working on it right now...hoping something might work.
devcon69 said:
on 8.6.11 its working
Click to expand...
Click to collapse
dhirenmathur said:
In the screenshots, you seem to be running 8.6.6, I tried that too, even tried signatures from different devices, but it doesn't seem to work. I can't seem to figure out why.
Click to expand...
Click to collapse
technology-informer said:
I am on RR rom in redmi note 5 pro Indian version. I followed the same steps as said and rebooted the phone and got safetynet check as true for cts profile. So I try to login to tez but it showed error telling that I am running on custom rom. So I checked cts profile, it was still true. But once I rebooted again and checked it was false again
Click to expand...
Click to collapse
technology-informer said:
This issue is fixed in the latest RR build
Click to expand...
Click to collapse
amitroutray said:
I am on the latest build of RR. But it is not working.
Triggered from RN5pro
Click to expand...
Click to collapse
I have gone through the process but failed. When I again tried to do I shows Edit device fingerprint (disabled) want to know how to bring back to Previous stage. I am also flashed the Universal safety net. Is it disabled for that reason??
Triggered from RN5pro
amitroutray said:
I have gone through the process but failed. When I again tried to do I shows Edit device fingerprint (disabled) want to know how to bring back to Previous stage. I am also flashed the Universal safety net. Is it disabled for that reason?? View attachment 4525994
Triggered from RN5pro
Click to expand...
Click to collapse
Remove universal safety net module. Busy with my exams. Will be free in a month. Will try to add few more steps as soon as i find some free time.
Sent from my Redmi Note 5 Pro using Tapatalk
just flash universal safety net fix.. tez is working fine!
Hi,
Work with Miui 10 ?
Regys said:
Hi,
Work with Miui 10 ?
Click to expand...
Click to collapse
yes
learnerz said:
yes
Click to expand...
Click to collapse
With Mi 5 too ?
This was working for me the first time I tried. But now after booting my phone I noticed my bank app (which is selected in magisk hide) crashing, so I run safetynet test again and it fails. So try procedure again, also with different fingerprints but it keeps failing the test now (ctsProfile: false)
Im running RR Oreo 20180706 Official ROM, magisk 16, no xposed.. Are the fingerprints outdated or something? Why it worked it first time but not anymore?
Not working in Mi Note 5x.
OS MIUI 9.6 stable
Still failed the ctsProfile
Kapiljhajhria said:
Adding more steps. Will do it tomorrow. Also this is for cts profile mismatch. Sometimes magiskhide doesn't work properly on se roms. Last few miui version is having issue. From what i could figure out it might be due te selinux state. Magiskhide is not able to hide that. Working on it right now...hoping something might work.
Click to expand...
Click to collapse
Can someone share kenzo active fingerprint pleaseeeee
mine works totally fine. running PE 9.0

REAL Enable AI Camera on Redmi Note 5 Pro via Magisk! Working AI Scene Detection!

Enable AI camera on Redmi Note 5 Pro whyred (MN5PRO) via Magisk module!
REAL enable AI Camera, the only one with working AI scene detection!
I have try more than ten mods for AI camera but i think this is the best (other mods just seeing the AI option but nothing else to knowing if working), from all that I tested
- is the only one that can auto recognize scene (you can see the attached photo, camera shot a plant and AI recognize that),
- works with stock miui camera,
- have the less effect on your ROM
- and you can easy uninstall it via magisk manager.
- also enable 4k video recording, full manual mode, front camera HDR and maybe more.
You must have installed magisk root and then install this module via magisk manager. (but you can also install this module via TWRP (i have try it). ... edit and deleted because of post #4)
Works on every MIUI version, stable or beta!
edit
checked on miui 9.3.28 (android pie) and unfortunately don't work the auto AI scene detection
So this patch not only enable the AI camera option, also enable 4k video recording, front HDR, full manual mode. For manual mode (only for this, not for AI camera option etc) maybe you must have enabled camera2api.
How to enable camera2api?
Root > copy with RootExplorer (or similar app) system/build.prop to other location into internal storage > open it and add string 'persist.camera.HAL3.enabled=1' (if not exist), save and copy the build.prop back to system (replace the original) > give it the permissions "rw-r--r--" or 644, reboot. On some cases (custom ROM etc) maybe must do the same work with vendor/build.prop
{
"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"
}
You can download from here https://drive.google.com/file/d/1T-0Q79D5QNxlslEB4r9Pq_9qEYhjEklW/view
I find it here (you can download also and read more about that and you can see more photos, review etc)
http://en.miui.com/thread-4747165-1-1.html
but into zip archive is an read me file that say "Modul ai kamera whyred By: kubil hadinata"
so the credits must goes to Otrov and to creator (i think) kubil hadinata ... more for kubil hadinata here
Thanks alot, works great! Just used this on latest Revolution OS on note 5 pro global - works great
Can it be installed through TWRP too as mentioned in the instructions?
I tried but not able to flash.
RKStyles said:
Can it be installed through TWRP too as mentioned in the instructions?
I tried but not able to flash.
Click to expand...
Click to collapse
o, maybe this works for me because i have already magisk root installed, so i am sorry and i will edit the 1st post
It works, but It seems it's not compatible with gcam patches. If I install both modules (AI and gcam patch), the MIUI camera works regularly but AI isn't recognizing any scene
I'm on ArrowOS 9.0 Pie (RN5 Global)
EDIT: it seems that this module already contains the gcam patch! (60 fps video recording, front HDR+ shots and 240 fps Slow Motions work perfectly)
@EdoNINJA93 Yes, this patch not only enable the AI camera option.
Also enable 4k video recording, full manual mode, front camera HDR and maybe more. Maybe you must have enabled camera2api (i will edit the 1st post)
Working fine with resurrection remix official rom.
Thanks for sharing.
furchtlos76 said:
Thanks alot, works great! Just used this on latest Revolution OS on note 5 pro global - works great
Click to expand...
Click to collapse
Revolution os aosp ? Or miui ? Or caf ? Which one are you using tell me about your experience please
irfankamal said:
Revolution os aosp ? Or miui ? Or caf ? Which one are you using tell me about your experience please
Click to expand...
Click to collapse
Miui
Thanks a lot .. it works fine on my device,I m using miui stable rom
not the first one to recognize ites with AI
there was one a few months ago.
raptorddd said:
not the first one to recognize ites with AI
there was one a few months ago.
Click to expand...
Click to collapse
i am sorry, i don't know that, please tell me about and give me a link
so i edit the 1st post
"...from all that I tested
- is the only one..."
And please can someone to answer in my question
thanks
ps
apologize for double post but i am confused about that, please to answer me here or to other thread
This module is not working properly. Although the AI is functioning, and is able to detect the scene, but the camera fails to capture image. As soon as I press the shutter, the camera app crashes, and the photo is not saved. When I turn off AI, this problem doesn't occur. If possible, kindly provide a fix for this bug.
Device : RN5 pro (Indian variant with Sony IMX486 sensor)
ROM: Havoc OS (9.0 pie)
Shaurya117 said:
This module is not working properly. Although the AI is functioning, and is able to detect the scene, but the camera fails to capture image. As soon as I press the shutter, the camera app crashes, and the photo is not saved. When I turn off AI, this problem doesn't occur. If possible, kindly provide a fix for this bug.
Device : RN5 pro (Indian variant with Sony IMX486 sensor)
ROM: Havoc OS (9.0 pie)
Click to expand...
Click to collapse
thanks for your try but as you can see at the 1st post
"Works on every MIUI version, stable or beta! "
the problem is not the module but your rom i think...unfortunately i don't know if it is compatible with havoc os
Shaurya117 said:
This module is not working properly. Although the AI is functioning, and is able to detect the scene, but the camera fails to capture image. As soon as I press the shutter, the camera app crashes, and the photo is not saved. When I turn off AI, this problem doesn't occur. If possible, kindly provide a fix for this bug.
Device : RN5 pro (Indian variant with Sony IMX486 sensor)
ROM: Havoc OS (9.0 pie)
Click to expand...
Click to collapse
Do you have any other camera module? Uninstall it/them, this AI module has everything already included (also gcam patch)
EdoNINJA93 said:
Do you have any other camera module? Uninstall it/them, this AI module has everything already included (also gcam patch)
Click to expand...
Click to collapse
I don't have any other camera module/patch installed. Not even GCAM patch. GCAM works flawlessly on my Indian RN5 Pro without any patch.
Where is you find the patch. who is the author of this patch ?
is this module only for miui rom?
im on syberia. this module doesn't work
ai mode on, off There was no difference
Sent from my Redmi Note 3 using Tapatalk
tommyFeb said:
is this module only for miui rom?
im on syberia. this module doesn't work
ai mode on, off There was no difference
Click to expand...
Click to collapse
please read the 1st post, is only for miui

Magisk Addons - Which ones do you use and why?

Hello everyone, i came from the 5T and am happy about the 8T, I hope you enjoy the 8T so far too!
My question for you guys is what Magisk addons are you using with the 8T and why?
Which addons are you still waiting for?
Post your addon-list and write why you use them.
My Addons (current):
- Energized Protection ## Ad-Blocker, battery friendly.
- Busybox for Android NDK ## Busybox binary, must have.
- Audio Modification Libary ## to use Viper4Android
- Viper4AndroidFX ## works now on Android 11, but you cannot select profiles (current)
- Systemless Host ## for a better work of the AD-Blocker
Pretty much the same except adaway over energized.
{
"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"
}
Sent from my KB2005 using Tapatalk
Just an information, I found a working zip file for Viper4Android.
In this youtube video its explained:
https://www.youtube.com/watch?v=ltbJryJT1gg&feature=youtu.be
Its only a flash of the zip file without any additional modules like AML and stuff. For me this works
smouker said:
Just an information, I found a working zip file for Viper4Android.
In this youtube video its explained:
https://www.youtube.com/watch?v=ltbJryJT1gg&feature=youtu.be
Its only a flash of the zip file without any additional modules like AML and stuff. For me this works
Click to expand...
Click to collapse
OMG yes thank you! I can't live without V4A. It's the only reason why I have to root.
Sent from my KB2005 using Tapatalk
Wilazn said:
OMG yes thank you! I can't live without V4A. It's the only reason why I have to root.
Sent from my KB2005 using Tapatalk
Click to expand...
Click to collapse
Well then we are sitting in the same boat
Living without Viper4Andorid is a pain
smouker said:
Just an information, I found a working zip file for Viper4Android.
In this youtube video its explained:
https://www.youtube.com/watch?v=ltbJryJT1gg&feature=youtu.be
Its only a flash of the zip file without any additional modules like AML and stuff. For me this works
Click to expand...
Click to collapse
This didn't worked for me.. still error that I cannot install the drivers
paper88 said:
This didn't worked for me.. still error that I cannot install the drivers
Click to expand...
Click to collapse
I also have this issue. I used the link from the youtube video. I'm unable to get it to install drivers even after granting Viper4Android root access. Always get a "installations failed at patching system"
paper88 said:
This didn't worked for me.. still error that I cannot install the drivers
Click to expand...
Click to collapse
JWhetstone02 said:
I also have this issue. I used the link from the youtube video. I'm unable to get it to install drivers even after granting Viper4Android root access. Always get a "installations failed at patching system"
Click to expand...
Click to collapse
If you go to the v4a thread on here and download the latest Viper4Android apk from xda labs, it will work. They made it compatible with Android 11 now. Should be version 2.7.2.1
Install the apk, open it and follow instructions. After you grant it root access it will create a magisk module, install the driver and reboot your phone.
All has been working fine for me and I do not have any other sounds modules installed.
- Fullscreen/Immersive Gestures - a must have if you use built-in gestures
- Viper
- Systemless Host for AdAway
Sent from my OnePlus8T using XDA Labs
sharkie405 said:
- Fullscreen/Immersive Gestures - a must have if you use built-in gestures
- Viper
- Systemless Host for AdAway
Sent from my OnePlus8T using XDA Labs
Click to expand...
Click to collapse
I think that gesture module is obsolete on our device, there is an option to hide the bar in system as it is.
fxz said:
I think that gesture module is obsolete on our device, there is an option to hide the bar in system as it is.
Click to expand...
Click to collapse
Yes, but hiding the bar using that setting breaks swiping the bottom to go to previous app. This module hides the bar while keeping that functionality in tact.
Sent from my OnePlus8T using XDA Labs
They updated V4A on magisk. It works on Android 11 now.
Sent from my KB2005 using Tapatalk
Anyone tested Dolby module? If it's better than the pre installed version. Not rooted myself yet and would if I could
smouker said:
Well then we are sitting in the same boat
Living without Viper4Andorid is a pain
Click to expand...
Click to collapse
What makes V4A so good?
Wilazn said:
They updated V4A on magisk. It works on Android 11 now.
Sent from my KB2005 using Tapatalk
Click to expand...
Click to collapse
V4A works now, but you cannot select profiles such as bluetooth, speakers, etc. In addition, not all functions can be selected.
Super-Veloce said:
What makes V4A so good?
Click to expand...
Click to collapse
V4A is so popular because it allows you to create individual profiles in which you can set not only more bass or treble, but also a lot more parameters in the sound / equalizer settings.
You just have to test it for yourself and find out. For example, I found out a function that produces such a clean bass for my car, without V4A I would never have found that my speakers in the car can do so much without sounding bad. In addition, you can e.g. for Bluetooth increase the master sound (in dB).
Yea I noticed after I posted. I copied all my presets from my previous phone and nothing shows up. Sucks there's no profiles for speaker, headset, Bluetooth, etc. Hope the fix comes soon.
Sent from my KB2005 using Tapatalk
any module for automatic call recording?
Ramme said:
V4A works now, but you cannot select profiles such as bluetooth, speakers, etc. In addition, not all functions can be selected.
V4A is so popular because it allows you to create individual profiles in which you can set not only more bass or treble, but also a lot more parameters in the sound / equalizer settings.
You just have to test it for yourself and find out. For example, I found out a function that produces such a clean bass for my car, without V4A I would never have found that my speakers in the car can do so much without sounding bad. In addition, you can e.g. for Bluetooth increase the master sound (in dB).
Click to expand...
Click to collapse
How to activate V4A? I installed and activated the module but there's no difference with or without equalizer on phone speakers. V4A shows the same as your screenshots.
Did any of you get adaway working? Chrome beta is still showing ads ?
Layze said:
Did any of you get adaway working? Chrome beta is still showing ads [emoji19]
Click to expand...
Click to collapse
I don't think adaway completely removes the Google ads? I have the shopping ads but when I click them they refuse connection.
Ads on other sites though are removed for me. And ads on games are completely blocked.
Sent from my KB2005 using Tapatalk

[OFFICIAL] LineageOS 19.1 for the Moto One Action/One Vision/P50

{
"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 One Action/One Vision/P50
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Moto One Action/One Vision/P50.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly.
Moto One Action
troika - Official builds
troika - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.
Moto One Vision/P50
kane - Official builds
kane - My unofficial with Google Apps/Pixel goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
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.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_motorola_exynos9610
Good afternoon. Please fix NFC.
How do I make the stock one pass the safety net without rooting (the same way the unofficial image you posted does)?
Can't find any tutorials online
misiupysiu said:
How do I make the stock one pass the safety net without rooting (the same way the unofficial image you posted does)?
Can't find any tutorials online
Click to expand...
Click to collapse
Doesn't pass by default, was a typo.
eilujx said:
Good afternoon. Please fix NFC.
Click to expand...
Click to collapse
looking into it - didn't know it didn't work.
npjohnson said:
looking into it - didn't know it didn't work.
Click to expand...
Click to collapse
Thanks! It turns on but doesn't work.
eilujx said:
Thanks! It turns on but doesn't work.
Click to expand...
Click to collapse
Got it isolated, it's selinux. Will be fixed hopefully next build.
EDIT: Wait, it works without the fix lol
eilujx said:
Good afternoon. Please fix NFC.
Click to expand...
Click to collapse
Just tried it on my troika - it works fine. Do you have kane, troika, or P50?
npjohnson said:
Doesn't pass by default, was a typo.
Click to expand...
Click to collapse
Weird, my banking app works on your unofficial build but doesn't work on the official one. Any idea which of the additional things you installed might be responsible? Are you able to post the changes you made to the unofficial build so I can try to isolate it?
I'm using the troika image.
Sorry for bothering you, I really want it to work.
npjohnson said:
Just tried it on my troika - it works fine. Do you have kane, troika, or P50?
Click to expand...
Click to collapse
mine is kane
npjohnson said:
Got it isolated, it's selinux. Will be fixed hopefully next build.
EDIT: Wait, it works without the fix lol
Click to expand...
Click to collapse
I just tested it again and it didn't work And it's not a problem with my phone, in stock it worked
misiupysiu said:
Weird, my banking app works on your unofficial build but doesn't work on the official one. Any idea which of the additional things you installed might be responsible? Are you able to post the changes you made to the unofficial build so I can try to isolate it?
I'm using the troika image.
Sorry for bothering you, I really want it to work.
Click to expand...
Click to collapse
Huh that is interesting, the manifest for the build is public in the manifest folder on my site download.ods.ninja
I'm running official ROM on Kane. Everything seems to be fine but the screen colours, which are a little off, even though I followed the wiki instructions.
I am running lineage 19.1 and It ia verry smooth like the lineage 18.1, the only issue is the safetynet on the oficial build. But for me everything is working Fine.
Does your unofficial build pass SafetyNet?
Seen a comment around saying that it was a typo.
georg3_ said:
Does your unofficial build pass SafetyNet?
Seen a comment around saying that it was a typo.
Click to expand...
Click to collapse
no it doesn't.
First of all thank you for choosing ONE ACTION as a part of Official device. You are developing very best but any how can solve the safety net issue? Please it is the problem why I can't be able to experience it very smoothly.
Once again thank you
Suman14_10 said:
First of all thank you for choosing ONE ACTION as a part of Official device. You are developing very best but any how can solve the safety net issue? Please it is the problem why I can't be able to experience it very smoothly.
Once again thank you
Click to expand...
Click to collapse
Try Magisk, find a way to make it work, let me know.
I was able to get safetynet working on the One Action official build with MindTheGapps by following the below steps:
You need to install these modules in magisk:
- Shamiko
- MagiskHide Props Config
- Universal SafetyNet Fix
- If you want to use Google Pay install Gpay SQLite Fix
For props config you want to edit device fingerprint to an android 12 supported devices (i used pixel 5) and force BASIC key attestation (i used pixel 5 again). Then just use denylist on GSF, Play Store (im not sure if its needed) and any other app you want to hide root from. Make sure you disable Enforce Deny List. Then you can clear data from Play Store, GMS, and Google Pay (if you need it). Google Pay might not work immediately (took a couple of reboots to get it to work) and Netflix and other apps might not appear in the Play Store at first.
SafetyNet passes now and I have access to Netflix, Google Pay, and my banking apps.
npjohnson said:
Try Magisk, find a way to make it work, let me know.
Click to expand...
Click to collapse
I'm trying to do so. But
Recently I've faced one more issue with CAMERA. The issue is attached with the screen recording please see the VIDEO.
after click an image not saving and the camera is still processing in background And the background processing is doing LAGGY to full system. Full system is lagging after click an image it is a bug or else..
Thank You #npjohnson

Categories

Resources