I installed the bgZ-lite version on my BV9600E (MediaTek 6771). I found that it passes SafetyNet and CTS and is SELinux enforcing! It identifies the phone name correctly. Encryption is offered as an option (haven't tried it yet). It is small enough to fit in the standard /system partition on the BV9600E, although I had already increased mine with parted. Looks really interesting Congratulations to the dev.Yesterday I have flashed " caos-v310-210721-arm64-bgZ.img " on my Blackview BV9600E and works perfect. I have used BLESS 14.2 before and sometimes phone reboots by itself.
From yesterday, using this CAOS v310 ROM, phone has not reboots.
Only has a little "problem": My phone left side buttom cannot be used. Has no function. I must install an APK to use it (BUTTOM MAPPER - https://play.google.com/store/apps/details?id=flar2.homebutton&hl=es&gl=US ).
Good work. Congratulations.
yes, need a proper treble overlay for your device https://github.com/phhusson/treble_experimentations/wiki/How-to-create-an-overlay?
1. seems your phone have eSIMHello. I'm facing 3 problems with GSI RROMs on my device of which i'm not getting any clew. With the nature of all these 3 problems, I'm thinking that is it something wrong with the Vendor? Even the Vendor partition didn't modified during ROM flashing. Kindly throw some light after reading details below:
1. My phone is showing 3rd sim slot, which is fake (phone has only 2). 3rd one is named as "china unicom" and has no Service/signals available. Upon first startup, the phone's language automatic set to chinese instead of my local due to this fake sim. also, Whenever there's a phone number field in any app, The country always pre-selected as "china" and code is "+86", instead of my active sims/local taratory.
2. Mobile network on GSI is too slow even with LTE 100% signals and videos buffers allot.
Stock: 35-40MBPS, GSI: 2-5MBPS.
3. Battery usage stats are unavailable even after having overlay present for my device under system/product/overlay.
Platform: MTK6768, mediatek G70 chipset.
Recovery: stock (no modification).
Bootloader: stock (no modification except unlock).
Device logs: Here
u:object_r:vendor_overlay_file:s0" and 644)
if you want proper fix then you need ask phhusson, i guess need add specific selinux ruleI've already known this. For example, I'm making a root script USB SampleRate Changer (on the fly) using these dumpsys commands internally. It doesn't use magisk specific functions, but works only under magisk environment. I don't like using "setenforce" commands in it invisibly.