Related
Will be any dev to work on RR,AEX & HavoC?
Those were all by our beloved Nfound, who has unfortunately moved on from the Axon 7.
Looks like the only options for updated builds are going to be the Lineage builds (14.1, 15.1, 16.0) , OR you could use generic treble GSIs which should almost be stable.(but won't be specific to our device.)
But for that we have to wait long time to get a stable treble
alwynjoshy said:
But for that we have to wait long time to get a stable treble
Click to expand...
Click to collapse
For me treble is very stable, I'm running pixelexperience and is great
J0nhy said:
For me treble is very stable, I'm running pixelexperience and is great
Click to expand...
Click to collapse
you have a link?
alwynjoshy said:
Will be any dev to work on RR,AEX & HavoC?
Click to expand...
Click to collapse
Who knows.
We've got Treble, but we still need some kind of universal patch for GSI roms to fix audio.
Everything else should work. (Personally, I didn't tried, staying with LOS 15 because of DAC)
Try latest AEX 5.8 from Nfound and Swifty R4 kernel.
xerocopy said:
Who knows.
We've got Treble, but we still need some kind of universal patch for GSI roms to fix audio.
Everything else should work. (Personally, I didn't tried, staying with LOS 15 because of DAC)
Try latest AEX 5.8 from Nfound and Swifty R4 kernel.
Click to expand...
Click to collapse
LOS 16 is the problem, and at least it hasn't got the crippling audio bug present in all B12 base builds. Of course having the DAC would be awesome, but I guess it all depends on getting the blobs from somewhere (though i have no idea of course)
I think 15.1 uses the DAC and hasn't got the audio bug but i'm not sure. Maybe the devs will end up fixing it if it does have it.
Zobat said:
you have a link?
Click to expand...
Click to collapse
Sure man,
https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
J0nhy said:
Sure man,
https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
Click to expand...
Click to collapse
Would you care to write how did you install image?
Only format System / Data and then flashing?
I'm currently on AEX 5.8 TREBLE with TWRP_3.2.1-8-TREBLE
And did you have any sound call isues with PixelExperience?
Thanks a lot
Choose an username... said:
LOS 16 is the problem, and at least it hasn't got the crippling audio bug present in all B12 base builds. Of course having the DAC would be awesome, but I guess it all depends on getting the blobs from somewhere (though i have no idea of course)
I think 15.1 uses the DAC and hasn't got the audio bug but i'm not sure. Maybe the devs will end up fixing it if it does have it.
Click to expand...
Click to collapse
AFAIK DAC works in LOS 16.
15.1 has the audio bug, even on the latest build. Orden didn't patch it, just for LOS 16.
LOS16 is the best choice right now. Smooth, NFC, Hotspot, DAC, no audio bug, etc. GSI are too problematic and laggy.
xerocopy said:
Who knows.
We've got Treble, but we still need some kind of universal patch for GSI roms to fix audio.
Everything else should work. (Personally, I didn't tried, staying with LOS 15 because of DAC)
Try latest AEX 5.8 from Nfound and Swifty R4 kernel.
Click to expand...
Click to collapse
Don't you have call bug on last treble AEX?
alwynjoshy said:
Don't you have call bug on last treble AEX?
Click to expand...
Click to collapse
Oh, you remind me something. I didn't have 'that' call bug.
Some people got problem on AEX 5.7/5.8 and other roms with call bug, it was caused LTE itself or Volte.
Try to change your APNs or Preffered Network Type to Global from LTE.
Edit: Check this thread.
I'm on A2017G LOS 15.1 (Schwifty R4 Kernel + LXT Glassfish profile), but I didn't get that bug when I was on AEX 5.8.
AEX 5.8 (with newer LOS 15.1 vendor and Schwifty R4) should be brillant. I will go back when new version of LOS 15.1 will comeout.
xerocopy said:
Oh, you remind me something. I didn't have 'that' call bug.
Some people got problem on AEX 5.7/5.8 and other roms with call bug, it was caused LTE itself or Volte.
Try to change your APNs or Preffered Network Type to Global from LTE.
Edit: Check this thread.
I'm on A2017G LOS 15.1 (Schwifty R4 Kernel + LXT Glassfish profile), but I didn't get that bug when I was on AEX 5.8.
AEX 5.8 (with newer LOS 15.1 vendor and Schwifty R4) should be brillant. I will go back when new version of LOS 15.1 will comeout.
Click to expand...
Click to collapse
My device is U model. I tried that way, changed to global but no improvement. But i noticed one thing that while ringing if i change the network mode or put the phone to flight mode tyen the calls went to voicemail so that we can identify that is the problem with rom. So far i got only one treble rom that has no call Error. ?️RR TREBLE ROM
alwynjoshy said:
My device is U model. I tried that way, changed to global but no improvement. But i noticed one thing that while ringing if i change the network mode or put the phone to flight mode tyen the calls went to voicemail so that we can identify that is the problem with rom. So far i got only one treble rom that has no call Error. ️RR TREBLE ROM
Click to expand...
Click to collapse
Whoa, NFound update his rom for Axon 7 yesterday!
AospExtended-v5.8-axon7-20180906-TREBLE.zip
Maybe he fixed that bug, I can't find anything on 4pda.ru. Sadly, he closed his own thread ona XDA.
Edit: Probably Sept. Security patches, nothing else.
xerocopy said:
Whoa, NFound update his rom for Axon 7 yesterday!
AospExtended-v5.8-axon7-20180906-TREBLE.zip
Maybe he fixed that bug, I can't find anything on 4pda.ru. Sadly, he closed his own thread ona XDA.
Edit: Probably Sept. Security patches, nothing else.
Click to expand...
Click to collapse
New AEX 8.1 build security patches are based on the OPM6.171019.030.K1 Nexus and has the latest sept.05 fixes (as the sept.01 fixes)
Code:
ro.build.id=OPM6.171019.030.K1
ro.build.version.security_patch=2018-09-05
xerocopy said:
Whoa, NFound update his rom for Axon 7 yesterday!
AospExtended-v5.8-axon7-20180906-TREBLE.zip
Maybe he fixed that bug, I can't find anything on 4pda.ru. Sadly, he closed his own thread ona XDA.
Edit: Probably Sept. Security patches, nothing else.
Click to expand...
Click to collapse
raystef66 said:
New AEX 8.1 build security patches are based on the OPM6.171019.030.K1 Nexus and has the latest sept.05 fixes (as the sept.01 fixes)
Code:
ro.build.id=OPM6.171019.030.K1
ro.build.version.security_patch=2018-09-05
Click to expand...
Click to collapse
Sadly this Rom also have the Call bug, the problems starts from second reboot, after clean install there were no issues but after from second reboot the problem starts, tried the global settings also
alwynjoshy said:
New AEX 8.1 build security patches are based on the OPM6.171019.030.K1 Nexus and has the latest sept.05 fixes (as the sept.01 fixes)
Sadly this Rom also have the Call bug, the problems starts from second reboot, after clean install there were no issues but after from second reboot the problem starts, tried the global settings also
Click to expand...
Click to collapse
Also AEX v6 GSI seems to be in the making (per NFound on telegram). We need a thread to exchange info & experience about these roms.
piet8stevens said:
Also AEX v6 GSI seems to be in the making (per NFound on telegram). We need a thread to exchange info & experience about these roms.
Click to expand...
Click to collapse
I tested the new AEX 9 build but it's almost the same as the AospExtended-v6.0-chiron-20180902-1012-ALPHA build from a couple of days ago floating on the MiMix2 net. I made a flashable zip of the build and as this one, it has a call bug, no NFC, not to many customs (as it is alpha...) (the Benzo rom or PE have way more customs atm and calls are working flawless...)
raystef66 said:
I tested the 'new' AEX 9 build but it's almost the same as the AospExtended-v6.0-chiron-20180902-1012-ALPHA build from a couple of days ago floating on the MiMix2 net. I made a flashable zip of the build and as this one, it has a call bug, no NFC, not to many customs (as it is alpha...) as the Benzo rom or PE who have way more customs atm...
Click to expand...
Click to collapse
Which /vendor do you use?
If I treblerize with LOS15. 1, can I flash any treble rom (GSI) ? Will encryption and restrictive selinux work?
What do you use currently as daily driver?
Have you tested latest NFound AEX5. 8 (from telegram - 20180906)? If so, with which /vendor?
piet8stevens said:
Which /vendor do you use?
If I treblerize with LOS15. 1, can I flash any treble rom (GSI) ? Will encryption and restrictive selinux work?
What do you use currently as daily driver?
Have you tested latest NFound AEX5. 8 (from telegram - 20180906)? If so, with which /vendor?
Click to expand...
Click to collapse
I'll always recommend the v1.1 NFounds way.
Benzo and PixelExperience are imo the best to use even as a daily driver. My focus is on Benzo as everything works beside the Hotspot (NFC is working with the @kountry83 NFC- fix ). Rest is flawless and a bunch of customization as I dont find that on other Pie's (only on PE). Even a 5hSOT with average use.
BenzoPie
PixelExperience
credits to them
What is this topic about?
I've spent quite some time writing fixes for GSIs to work properly on our Mi Max 3.
As part of that, we now have a list of easily flashable fully working Mi Max 3 ROMs to pick from.
This topic will be used to keep track of all fully working ROMs and of course to host the latest set of GSI patches / flash templates.
Available ROMs:
These have been tested and confirmed fully working (sans ROM-specific bugs).
AOSiP
Build date: 2019-05-14
Patch date: 2019-05-17
Flashing guide:
Unlock your device's bootloader.
Flash nijel8's modded TWRP recovery.
Pick and download one of the available ROMs.
Reboot into TWRP recovery and flash your ROM of choice.
Go into TWRP's wipe menu and "factory reset" your device (aka. slide the bar).
Flash Gapps (Opengapps / Bitgapps) if your ROM of choice requires / you want it.
Reboot your phone and set it up to your liking.
How can I get my ROM of choice listed here?
Download the TWRP package template from here!
Grab a GSI of your choice and unpack the system image (if it is compressed).
Rename the unpacked system image to system.img and place it inside the system folder inside the template zip file.
Rename the resulting zip file accordingly, flash it, test it, and after you've confirmed everything's working fine, upload and share it.
How do I enable DT2W (double-tap to wake)?
Create a file named "enable_dt2w" (without the quotes) in your device's internal storage.
Reboot your device.
Changelog:
2019-05-17
Changed cpusets to 0-7 (UX gains)
Set rendering thread to schedule as FIFO (UX gains)
Updated AOSiP to its latest (2019-05-14) build
2019-05-10
Swapped firmware & vendor base to stable 10.3.1.0
Updated AOSiP to its latest (2019-05-07) build
2019-05-01
Added two touchscreen-related properties to build.prop
2019-04-30
Updated the kernel to ResurrectedKernel 5.0 (brings a whole bunch of new governors)
Changed default little core governor to alucard
Changed default big core governor to darknessv5
Updated AOSiP to its latest (2019-04-29) build
2019-04-22
Fixed a mistake on my end that made the screen flicker on brightness changes (sorry guys)
Updated the kernel to ResurrectedKernel 4.1 (kcal support!)
Updated AOSiP to its latest (2019-04-22) build
2019-04-21
Fixed the device fingerprint issue (Magisk users should now be CTS-verified by default again)
Added AptX & AptX HD Bluetooth support
Removed DotOS & PixelExperience from the rooster because the WiFi HotSpot function wasn't working properly in them
2019-04-12
Added addon.d support (which means dirty-flashes won't lose their Gapps, Magisk, etc. anymore)
Tested and added Pixel Experience to the roster
2019-04-10
Added ResurrectedKernel (Unlocks 1.8GHz on Little Core / 2.0GHz on Big Core)
Tweaked Governor to utilize ResurrectedKernel's frequency range fully
Updated DotOS bundle to latest build
Repacked all bundles with latest patch
Dropped "Minimal Package" support as its no longer maintainable in tandem with ResurrectedKernel
It ended up with the lags (AOSIP).
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Germano1980 said:
It ended up with the lags (AOSIP).
Click to expand...
Click to collapse
Where's the lag Germano? Works fine for me.
Jesenican said:
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Click to expand...
Click to collapse
Stuck how? If you have "unlock" trouble, as in, your PIN won't let you in, use the "Remove lockscreen" option inside TWRP to remove your previous lockscreen data.
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
MrColdbird said:
Where's the lag Germano? Works fine for me.
Click to expand...
Click to collapse
Before installing their zip, they had some lags in screen transitions and to slide and open apps. Now, everything got more fluid and faster. It was great ... until voLTE is working (and my operator informed me that my device was not compatible with haha).
---------- Post added at 19:14 ---------- Previous post was at 19:07 ----------
Jesenican said:
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
Click to expand...
Click to collapse
What vendor is your device on? Many GSI's only start at a particular vendor (Oreo or Pie).
Jesenican said:
No no, when you reboot your phone there is first MI logo and unlocked sign at bottom. I cant get pass that screen.
Click to expand...
Click to collapse
Make sure the GSI you picked supports Pie vendors.
Not every GSI does... and the ones that are still stuck on Oreo vendors are... troublesome, to say the least.
AOSiP supports pie vendor and so does pixel experience but no luck. If i update recocery, will that help? I really wanna try one gsi if lag is now fixed.
Jesenican said:
I always stuck at unlocked screen, tried AOSIP, Pixel Dust and Pixel Experience, all the same. Any solution to this. Tried from latest xiaomi.eu beta. Thanks
Click to expand...
Click to collapse
The last time I had problems in booting the GSI roms I did the following:
1- I reinstalled the latest global version of Miui Oreo via miflash (Beware of ARB)
2- Logged in the Mi account, enabled the USB debugging and installation by ADB settings to install the TWRP
3- I installed TWRP (nijel8's modded), formatted the data and then installed xiaomi.eu
4- I configured the device and made a backup of xiaomi.eu
5- As I already had the files, I installed AOSIP, without deleting the system, just cleaning the data of xiaomi.eu
6- After the boot, I installed the gapps and magisk.
I never had any problems installing GSI's on my device.
When I was in Miui Oreo, I tested some roms that only boot the Oreo vendor (Bootleggers, PixelDust among others), but I think with the Oreo vendor they spend a little more battery life.
(hope this helps you)
guys, i want to try this but not trigger arb, with .eu or aosp, pixel experience etc.. i'll trigger it?
Masacci0 said:
guys, i want to try this but not trigger arb, with .eu or aosp, pixel experience etc.. i'll trigger it?
Click to expand...
Click to collapse
No ARB on xiaomi.eu as they don't ship firmware into it. No ARB on gsi of course. So no worry about it
Regards
Skyllery said:
No ARB on xiaomi.eu as they don't ship firmware into it. No ARB on gsi of course. So no worry about it
Regards
Click to expand...
Click to collapse
So if i install this rom https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-stable-release.47170/ i'm ok and without arb? I get confused because on the image they say mi max 3 has arb, if they mean the official 10.2 has arb, why even put the image in the .eu version? It just confuses people.
So i go with this rom reach setup screen, recovery and install the gsi rom?
Jesenican said:
AOSiP supports pie vendor and so does pixel experience but no luck. If i update recocery, will that help? I really wanna try one gsi if lag is now fixed.
Click to expand...
Click to collapse
Try the xiaomi.eu versions from last month based on installing AOSiP. Today I tried with the versions of this month and did not boot.
I am having the exact same issue. I followed the guide and installed the latest xiaomi.eu 9.3.7 beta and boot no problem then i flash gsi .img and it gets stuck at MI Logo and wont go any further. I have tried latest xiaomi.eu beta, stable, last months, month before that. All xiaomi.eu boot fine without issue but as soon as I flash any gsi .img it gets stuck at MI Logo screen? Am I doing something wrong?
Also the gsi i am using is latest pixel experience arm64 A only.
Any help would be greatly appreciated.
Same. I tried 3 different GSI roms and kept being stuck on the mi logo... :'(
only aosp gsi works, still getting android.process.media and bluetooth crashes
Edit: instead of com.android.media it was android.process.media
I tried installing Descendant_TwoDotOne. It stuck on the mi logo when pairing it with xiaomi.eu 9.3.7 & 9.3.1. It works perfectly when paired with xiaomi.eu 9.2.21 (or earlier version should work). I guess there may be some changes made to the 9.3 version vendor content leading to this problem.
jngiag said:
I tried installing Descendant_TwoDotOne. It stuck on the mi logo when pairing it with xiaomi.eu 9.3.7 & 9.3.1. It works perfectly when paired with xiaomi.eu 9.2.21 (or earlier version should work). I guess there may be some changes made to the 9.3 version vendor content leading to this problem.
Click to expand...
Click to collapse
You're my hero! That did the trick. ;D
So can i normaly flash older xiaomi.eu version without fear of ARB?
OP post updated with a new package.
Changelog:
Tweaked the governor to boost properly and use the 1.6 / 1.8GHz maximum little / big frequencies. (Everything's even smoother now~)
Android Q Beta 2 update Now available
Source: https://android-developers.googleblog.com/2019/04/android-q-beta-2-update.html
The release of Android Q Beta 2 QPP2.190228.021, which includes updated SDK for developers, bug fixes, improvements in performance and stability, and the April 2019 security patches.
There will be more consumer-facing features and capabilities added in the next release, which we’ll share at Google I/O in May.
New gestures:
https://9to5google.com/2019/04/03/android-q-beta-gestures-iphone/
Bubbles:
Bubbles are a new feature in Android Q. With bubbles users can easily multi-task from anywhere on their device. Bubbles are built into the Notification system. They float on top of other app content and follow the user wherever they go. Bubbles can be expanded to reveal app functionality and information, and can be collapsed when not being used.
Known issues for Beta 1 and Beta 2:
https://developer.android.com/preview/release-notes.html
Magisk v19 doesn't seem to work for me at all. I installed the apk separately also and it says it's not installed
castano22 said:
Magisk v19 doesn't seem to work for me at all. I installed the apk separately also and it says it's not installed
Click to expand...
Click to collapse
Topjohnwu is working on it!
https://twitter.com/topjohnwu/status/1113762418021236741
I had problem with my pixel 2xl after updating it started to restart it self and returned to stable pie back.
kemalcenk said:
I had problem with my pixel 2xl after updating it started to restart it self and returned to stable pie back.
Click to expand...
Click to collapse
I had the same problem after installing magisk on beta 1. the phone began restarting itself until it couldnt boot to desktop. i searched then but nobody was reporting the same issue so i gave up and reinstalled pie.
no issues here, i had to flash both booth partitions manually. been running beautiful
I figured out the problem. İf you use system in English everything perfect. For me changing system language to Turkish starts Bootloop when restarting.
Universal SafetyNet Fix
Magisk module
Magisk module to work around Google's SafetyNet attestation.
This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS profile attestation, which requires a valid combination of device and model names, build fingerprints, and security patch levels.
If you still have trouble passing SafetyNet with this module, use MagiskHide Props Config to spoof a certified device profile. This is a common issue on old devices, custom ROMs, and stock ROMs without GMS certification (e.g. Chinese ROMs).
Android versions up to 13 Beta 3 are supported, including OEM skins such as Samsung One UI and MIUI.
How does it work?
The way this workaround works is relatively low-level. An in-depth explanation, as well as source code and ROM changes, can be found on GitHub.
Ideally, this workaround should be incorporated in custom ROMs instead of injecting code with a Magisk module. See the ProtonAOSP website for more information.
Downloads
Downloads and changelogs can be found on GitHub. The topmost release is the latest.
Latest release
v2.4.0
Spoiler: Changelog
Highlights
Play Integrity bypass without breaking device checks or causing other issues
Disabled use of hardware attestation on Pixel 7 and newer (@anirudhgupta109)
Other changes
Updated instructions for newer Android and Magisk versions
Better debugging for future development
This version only supports Zygisk (Magisk 24 and newer).
It's taken a while to find a way to bypass Play Integrity that doesn't require spoofing the build fingerprint permanently, but I wanted to make sure this module doesn't cause any unnecessary breakage. Just like the original goal of Universal SafetyNet Fix, this minimizes adverse effects by spoofing dynamically at runtime only when necessary. Enjoy!
If you found this helpful, please consider supporting development with a recurring donation for rewards such as early access to updates, exclusive behind-the-scenes development news, and priority support.
Alternatively, you can also buy me a coffee. All support is appreciated
Source code
Note 8 pro Android 9 and Android 10 not working
Tested succesfully on Pixel 4a 5G, but Google Pay says "Your phone doesn't meet security requirements" even though PayPal can be set up.
Magisk Hide is activated.
Magisk says SafetyNet passes but Google Pay still doesnt
Dydnlee said:
Note 8 pro Android 9 and Android 10 not working
Click to expand...
Click to collapse
Please test it again with this version: https://github.com/kdrag0n/safetynet-fix/archive/e82c3d0674e6452938e49bc6ee6848aa2a603c27.zip
[QUOTE = "kdrag0n, gönderi: 84286879, üye: 7291478"]
Lütfen bu sürümle tekrar test edin : https://github.com/kdrag0n/safetynet-fix/archive/e82c3d0674e6452938e49bc6ee6848aa2a603c27.zip
[/ALINTI]
İnstall failed
Thank you a lot, Universal SafetyNet Fix v1.1.0 working excellent on Xiaomi Mi 9T, Xiaomi.eu 21.1.6, MIUI 12.5 / Android 11 Beta
Device certified but not using Google Pay
Safety net fix 1.0.2 worked for miui Eu 12.0.3.0 Android 10 for Poco F1.
Only that the ocbc bank Singapore app still able to detect the root and became unusable.
But I know that this doesn't relate to safetynet fix here because the issue already existed before the CTS false.
tylerdurden said:
Tested succesfully on Pixel 4a 5G, but Google Pay says "Your phone doesn't meet security requirements" even though PayPal can be set up.
Magisk Hide is activated.
Click to expand...
Click to collapse
Clear app data from Google pay aswell as Google play services.
Tested on Samsung S9:
- 1.0.2 worked in MM, but Root Checker said 'cannot access GPS'.
- 1.1.0 fails ctsProfile in MM, but Root Checker now can access GPS, also returns ctsProfile fail.
Massive thanks for this. Version 1.1.0 confirmed working on my device:
- Pixel 3, stock room
- Magisk 21.2, magisk manager 8.0.5
- Magisk hide enabled and magisk manager renamed
All banking apps and google pay work correctly, including contactless payments.
working on poco f2 pro,android 11,rom one os thanks
Tested on Huawei Mediapad M5 with EMUI 9.1.0 and Magisk 20.4:
- 1.1.0 fails ctsProfile in MM, basic integrity is ok
Working OK on Mi Note 10 Lite, Android 10 and ROM xiaomi.eu
Thanks
I tried this on my Samsung Galaxy A6 (official samsung firmware patched with magisk) - and even version 1.1.0 causes bootloop when using zip inside Magisk Manager - Android 10
Good morning. Working on Redmi Note 9 Pro xiaomi.eu 12.0.1 Android 10. No MagiskHide Props Config needed: basicIntegrity passed, ctsProfile passed, evalType BASIC.
Thank you so much
MI10 Global with V12.2.8 xiaomi.eu , used V 1.0.2 works
Thank you!
Works on pixel 3a, last A10 patch, using magisk hide props config to force basic attestation. Was already using mhpc so not sure if it works without it. Fixed my CTS issue though, so thanks!
@kdrag0n Thank you so much for this awesome masterpiece!
I find it a bit interesting, that I experience a problem which nobody else seems to have reported so far. I'm using a Galaxy S10 (Exynos, G973F), rooted with latest canary Magisk, no EdXposed or whatsoever...
If I enable this module, no bootloop, basic attestation, CTS passes. "Yes", so I thought...
The problem now... My bank app tries to access the keystore and crashes. This does not happen without having this module enabled... I have attached a fully logcat and hope that you have some insights...
EDIT1: re-attached file, didn't work on the first go.
EDIT2: oh... search for "easybank" or "keystore"
EDIT3: Android 11, One UI 3
POCO F1 user here. After flashing the module the phone stucks on the Google logo at boot.
The MHPC module didn't solve the problem either.
ROM: Pixel Experience 11 Beta (20201223)/Encrypted
Hello everyone, hope you're having a great day.
Recently I've installed OrangeFox Recovery as well as crDroid 9.5 on my RN7/lavender, all working fine, but by default I saw that the Pixel Spoofing feature is enabled by default.
Later on, I found as well that disabling it made my device be detected as a Pixel 5, rather than a RN7.
This is very annoying as I'm currently on the situation that I can't revert the Pixel Spoofing changes without rooting with Magisk or doing any other internal changes (e.g editing build.prop).
So, it comes up to my question regarding how can I delete completely Pixel Spoofing from the source code of crDroid lavender (https://github.com/crdroidandroid/android_device_xiaomi_lavender).
I've seen as well that the Pixel Spoofing feature is located on another crDroid repository that contains the "base" I guess for all devices (https://github.com/crdroidandroid/android_frameworks_base) (https://github.com/crdroidandroid/a...id/internal/util/crdroid/PixelPropsUtils.java).
I couldn't get any help on Telegram (Nexus Kernel), so if someone could help me figure out how to remove this feature and build the ROM, I'd appreciate it.
Thank you