if ill install Bootloader & TWRP & SuperSU & xposed to the Global rom, there is any chance for battery drain? I want xposed for 2 or 3 modules
thanks guys :good:
Arusy said:
if ill install Bootloader & TWRP & SuperSU & xposed to the Global rom, there is any chance for battery drain? I want xposed for 2 or 3 modules
thanks guys :good:
Click to expand...
Click to collapse
Not sure what you mean with "Install bootloader". If you Install TWRP, you can reduce screen brightness on TWRP settings to save battery. But most of us rarely working with TWRP for hours, so battery drain shouldn't be an issue.
With SuperSU, there'll be no issue with battery consumption. But if you install Magisk and activating Magisk Hide, a small amount of power consumption may affect to battery life.
Exposed Framework, in contrast, may costume more power especially if you install lot of modules or using very intense module working in the background.
If you need to maintain battery life against Xposed usages, consider to install custom ROM + custom kernel and tuning your device to work with profile or governor that more battery saver, as well as reducing CPU frequencies.
Arusy said:
if ill install Bootloader & TWRP & SuperSU & xposed to the Global rom, there is any chance for battery drain? I want xposed for 2 or 3 modules
thanks guys :good:
Click to expand...
Click to collapse
Bootloader : No
TWRP : No
Super su : No
Xposed : Not really
Thanks guys, just want to stick to global and use amplify & greenify root and xposed options and cancel whatsapp recipits thats it.
Related
(All credit goes to wanam for providing Xposed for TouchWiz roms)
I am not sure if this needs a thread but since i was searching for this information i'm making one for the Xposed fans with an A3 2017.
Because i don't have enough time to test more configurations i can't say if this will or will not work on any other configuration besides the one i have. Feel free to backup everything (using a recovery like TWRP or CWM) and try flashing Xposed yourself. Read the bottom of the post on how to get into your recovery when having a bootloop. I do not take any responsibility for bricked devices and any other damages.
I mostly followed the steps in this thread but i'll write the steps here as well.
This will only work with stock or stock-based roms, for AOSP based roms, use normal Xposed flashables
A recovery like CWM or TWRP (guide) is required.
Backup your /system partition or reckon that you might lose data. Flashing Xposed only affects /system
Install the Xposed 3.1 apk (requires "Unknown sources" to be allowed in system settings)
Go to your recovery by shutting down your phone and holding Volume Up + Home while powering it on
Flash this zip file for Xposed on Samsung devices (ARM). You might find newer versions here (choose ARM for this phone, not ARM64).
Reboot and wait for up to 15 minutes. It might bootloop a couple times and you might have to wait for app optimization for some more minutes
Enjoy the flexibility of Xposed
If your device is bootlooping for more than 10 minutes it's highly likely that Xposed is not working for you.
Note that using Volume Down + Power will restart your device but will always attempt to restart Android. In order to get to your recovery charge your device which will make VolDown + Power shut down the phone instead of restarting it. From there you can VolUp + Home and power it on to boot into recovery.
You can attempt to flash the uninstaller in order to fix the bootloop or if Xposed is just not working and you wanna get rid of it. If that doesn't help, restore your backup (will always work, flashing the uninstaller is just quicker).
Known bugs on the A3 2017:
- none (will add from comments or if i find any)
Sources:
https://github.com/wanam/Xposed
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
https://forum.xda-developers.com/sa.../samsung-sm-a520f-2017-kernel-source-t3557622
Hello,
why is arm64 version not working / 64bit ist not recognised by xposed?
It's definitely a 64bit CPU with arm64v8a instruction set (Aarch64).
So why the installation of arm64 is blocked?
SinusStudios said:
(All credit goes to wanam for providing Xposed for TouchWiz roms)
I am not sure if this needs a thread but since i was searching for this information i'm making one for the Xposed fans with an A3 2017.
Because i don't have enough time to test more configurations i can't say if this will or will not work on any other configuration besides the one i have. Feel free to backup everything (using a recovery like TWRP or CWM) and try flashing Xposed yourself. Read the bottom of the post on how to get into your recovery when having a bootloop. I do not take any responsibility for bricked devices and any other damages.
I mostly followed the steps in this thread but i'll write the steps here as well.
This will only work with stock or stock-based roms, for AOSP based roms, use normal Xposed flashables
A recovery like CWM or TWRP (guide) is required.
Backup your /system partition or reckon that you might lose data. Flashing Xposed only affects /system
Install the Xposed 3.1 apk (requires "Unknown sources" to be allowed in system settings)
Go to your recovery by shutting down your phone and holding Volume Up + Home while powering it on
Flash this zip file for Xposed on Samsung devices (ARM). You might find newer versions here (choose ARM for this phone, not ARM64).
Reboot and wait for up to 15 minutes. It might bootloop a couple times and you might have to wait for app optimization for some more minutes
Enjoy the flexibility of Xposed
If your device is bootlooping for more than 10 minutes it's highly likely that Xposed is not working for you.
Note that using Volume Down + Power will restart your device but will always attempt to restart Android. In order to get to your recovery charge your device which will make VolDown + Power shut down the phone instead of restarting it. From there you can VolUp + Home and power it on to boot into recovery.
You can attempt to flash the uninstaller in order to fix the bootloop or if Xposed is just not working and you wanna get rid of it. If that doesn't help, restore your backup (will always work, flashing the uninstaller is just quicker).
Known bugs on the A3 2017:
- none (will add from comments or if i find any)
Sources:
https://github.com/wanam/Xposed
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
https://forum.xda-developers.com/sa.../samsung-sm-a520f-2017-kernel-source-t3557622
Click to expand...
Click to collapse
knzsys said:
Hello,
why is arm64 version not working / 64bit ist not recognised by xposed?
It's definitely a 64bit CPU with arm64v8a instruction set (Aarch64).
So why the installation of arm64 is blocked?
Click to expand...
Click to collapse
To be honest i flashed 32 bit xposed because i searched for the phones architecture and found 32 bit but that must be a misinformation.
I'm surprised now that it's working on my phone!
Thanks for mentioning this, if you have time feel free to safely try out both versions and report back what's working and what's not.
knzsys said:
why is arm64 version not working / 64bit ist not recognised by xposed?
It's definitely a 64bit CPU with arm64v8a instruction set (Aarch64).
So why the installation of arm64 is blocked?
Click to expand...
Click to collapse
Can't find a reason why our 64-bit phone is not recognized bit the 64-bit Xposed
I you want to install the 64-bit Xposed: got through Magisk
Don't know if it has a direct link: had lotz of reboot with 32-bit Xposed; nearly no reboot with 64-bit Xposed.
PS: Don't get too addict to Xposed has it will stop running when we'll get Nougat
The 64bit version will not work because Samsung shipped the SM-A320F with 32bit Android, even though it has a 64bit-capable SoC.
Im Wondering something here ... 32 bit os on our phone, no custom roms .. etc ... but the J7 2016 has the same CPU, same ram, storage, screen res ... you get the point .. i just wonder if a rom from that would ... and its 64 bit ... i mean, its the same damm SoC
are there any news for android 7 to get xposed without magisk. I have supersu root
y2kadir said:
are there any news for android 7 to get xposed without magisk. I have supersu root
Click to expand...
Click to collapse
Yes, you just have to search the Xposed thread and read.
Pat750 said:
Yes, you just have to search the Xposed thread and read.
Click to expand...
Click to collapse
ok but I just did it and coulnd`t find anything. can you tell me where to find?
y2kadir said:
ok but I just did it and coulnd`t find anything. can you tell me where to find?
Click to expand...
Click to collapse
Well I did, but if you can't even find it, I think it's better for you not to use it. Sorry.
Pat750 said:
Well I did, but if you can't even find it, I think it's better for you not to use it. Sorry.
Click to expand...
Click to collapse
why are you talking foolish ****. if you don't wanna help other people go home.
y2kadir said:
why are you talking foolish ****. if you don't wanna help other people go home.
Click to expand...
Click to collapse
OK here's something to start with.
https://forum.xda-developers.com/showthread.php?t=3034811
but please read the threads there are some good advice's.
Pat750 said:
OK here's something to start with.
https://forum.xda-developers.com/showthread.php?t=3034811
but please read the threads there are some good advice's.
Click to expand...
Click to collapse
I only found this in the thread "The first fixes have found their way into version 88.1, only available for Nougat. That includes especially some fixes for Samsung ROMs, but might also fix bootloops and slowdowns on other devices. Besides that, I think I fixed a MIUI incompatibility, not sure if it works now (and to be honest, I don't give much priority to MIUI). There are still unfixed issues on the queue, and again, please keep reporting whatever you find." but this information is not confirming me that its working.
Stock ROM 7.0 + Magisk + Xposed
Code:
This might be my first ever thread on xda, but am a part of this community sincebirth of galaxy y, that makes me aware of most of the android ROM terms and functioning.
So recently I rooted my 4 months old Lenovo k6 power to boost up my little beast. Tried different custom offical ROMs which includes RR, AOSPX, etc.
What I observed among them was:
Performance:Overwhelming
Stability: Up to the mark
Customizations: Sufficient
Battery? : HUNGRY!
My stock 7.0 used to give 2x times battery compared to what I was getting through these ROMs. //I confirm that it was a clean flash.
Now in order to understand whats wrong with these ROMs I opened CPU-Z and had a look on it.
Everything seemed perfect except one thing!
The phone inherits a SnapDragon 430 octa-core processor AND the observation was none of the cores were STOPPED even while my phone was IDLE completely.
Check attachment to see how it looks in STOCK. I didnt take any SC while on a custom ROM but I remember it well. One may provide with in comments?
Now here comes the problem, there seems NO HOT PLUG extension.
Qualcomm by default provides it by its "mpdecison" - but the ROMs failed to provide that option nor it was available through Kernel Auditor.
Pretty sure I'm not the only one facing it.
So here's what I did to acheive my desires:
NOTE: This will ENCRYPT your device again, you need to FORMAT DATA for TWRP fucntioning!
Reverted back to Stock ROM through this wonderful guide: https://forum.xda-developers.com/k6-power/how-to/guide-t3663065
Updated to latest via OTP
Installed Magisk for ROOT
https://forum.xda-developers.com/apps/magisk
This way I got stock which gives me day long BATTERY and root which passes SAFETY NET CHECK. (Attached)
And for customizations I'll by relying on systemless magisk Xposed Module.
Any thoughts on this?
Official Oreo has finally been leaked thanks to @NFound and since I've been extensively testing it this thread will be to teach you how to install it and to tell you what works and what doesn't.
Special THANK YOU to @NFound, @raystef66, @DrakenFX, @Oki, @WesTD and to everyone else who has helped with the development of the Axon 7 and with this thread
How to unlock the bootloader?
Follow this guide https://forum.xda-developers.com/axon-7/how-to/guide-unlock-bootloader-easily-t3704595 by @WestTD
Unlocked bootloader message removal:
Have not found a working method yet.
Always backup your intSD before flashing ROMs and other TWRPs (Recoveries)
Stock user, need to install TWRP?
Flash TWRP 3.2.1-0 https://androidfilehost.com/?fid=673791459329066789 by @raystef66
If you already have TWRP installed, any version will do since the ROM will replace it with TWRP 3.2.1-6 after installation.
Installation:
Download: https://androidfilehost.com/?fid=818222786056032764 (I hope this is allowed now, please forgive me if the links is still not allowed by XDA)
Move the .ZIP into your internal memory as you would by moving any other file into your phone through USB.
Boot into TWRP: adb reboot recovery or by turning the phone off and pressing VolUp+Power
Do a full backup!
Wipe to perform a clean install. Recommended.
Press Install
Select the .ZIP
Install with TWRP only! During installation it will be asked which modem you want to install. In my case this was the A2017G but that might not be yours. Please select correctly.
Wipe Cache and Dalvik Do not reboot yet if you want to root.
Rooting Download and install Magisk V16.4 or V16.0 exactly as you just installed the ROM.
Flash the safetynet fix linked below.
Wipe Cache and Dalvik
Reboot
Edit: Changing partitions to ext4 might be necessary for some non-stock users on f2fs.. Still updating
What's not working and how to fix it:
Magisk doesn't pass Safetynet? (ctsProfile: False). Download and flash https://androidfilehost.com/?fid=674106145207489292 Thank you @raystef66
Google play store shows as uncertified? The .ZIP above from @raystef66 fixes this as well. Your device is now certified.
How do I disable force encryption? Go to post #63 by @DrakenFX
Bad battery life? Flash Jojoc V2.1 or V3.1 module within Magisk or via TWRP V3.2 : https://androidfilehost.com/?fid=962187416754476535 V2.1 : https://androidfilehost.com/?fid=673956719939820457 by @raystef66
AdAway cannot install hosts file: Open Magisk -> Settings and select Systemless hosts.
Daydream is not working? Check post #23 B12 Thread by @kountry83 Download: Daydream.zip
How do I enable or disable the Navigation bar?: Check thread [A2017G][TWRP-ZIP]NAVIGATION BAR Enabler/Disabler by @raystef66 or Direct Link download for aroma installer
How do I remove the carrier label and center the clock on the status bar? Check thread [PATCH][A2017X V1.3.0B01] Remove Carrier & Center Clock by @raystef66 Download: A2017X_V1.3.0B01_carrier&clock
Remove carrier label only: Check post #342 by @raystef66 Download: A2017X_V1.3.0B01_carrierremover
Need modems, boot or bootstack? Download below by @raystef66
Modems:
ZTE_A2017X_Oreo_V1.30B01_Gmodem
ZTE_A2017X_Oreo_V1.30B01_Umodem
ZTE_A2017X_Oreo_V1.30B01_CNmodem
Boot:
A2017X-O_beta-B01-boot
Bootstack: twrp 3.2.1.6 included
ZTE_A2017X_V1.3.0B01_OREO_BootStack_twrp3216
What's working:
Pretty much everything other than what I wrote above it seems. The ROM is very fast and stable, my phone feels considerably snappier than it did on stock Nougat and there doesn't seem to be many bugs at all. Only thing I've noticed is the battery life doesn't seem to be great but that could just be some installed apps or my phone. Fixed by Jojoc V3.2 by @raystef66. Link above.
Testing Camera...
Working HDR+ Patch by @NFound: : HDR+ for v1.3.0 B01
GCAM: GCAM
Flashed an older version of that HDR+ Patch by @NFound and does your Magisk not pass the safetynet anymore? Flash this safetynet fix by @raystef66: A2017X-V1.30B01_safetynet_fix_HDR
Dual Sims: Fully working
I'll continue updating the thread according to your feedback and my testing.
Victor13f said:
Official Oreo has finally been leaked thanks to @NFound and since I've been extensively testing it this thread will be to teach you how to install it and to tell you what works and what doesn't.
Thank you @NFound once again for your hard work!
Thank you @Oki for having written https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693 If you need a better guide visit this thread and follow this guide simply using different files and not installing the bootstack separately.
How to unlock the bootloader?
Follow this guide https://forum.xda-developers.com/axon-7/how-to/guide-unlock-bootloader-easily-t3704595 by @WestTD
Unlock boot message removal:
If you want to remove the unlocked bootloader message at boot, you just need TWRP Exclusive. Just boot to recovery and go to the Advanced Menu -> More -> Del Inscription. You must to do this every time you update the bootloader. Thank you @Oki
Need to install TWRP?
Flash TWRP exclusive by @NFound https://androidfilehost.com/?fid=673956719939822011
Installation:
Download: https://androidfilehost.com/?fid=818222786056032764 (I hope this is allowed now, please forgive me if the links is still not allowed by XDA)
Move the .ZIP into your internal memory as you would by moving any other file into your phone through USB.
Boot into TWRP or ADB: adb reboot recovery or by turning the phone off and pressing VolUp+Power
Press Install
Select the .ZIP
Install with TWRP only! During installation it will be asked which bootstack you want to install. In my case this was the A2017G but that might not be yours. Please select correctly.
Wipe Cache and Dalvik Do not reboot yet if you want to root.
Rooting Download and install Magisk V16.4 or V16.0 exactly as you just installed the ROM or with TWRP Exclusive go to Advanced -> More -> Root -> Magisk
Wipe Cache and Dalvik
Reboot
What's not working?:
Magisk root doesn't pass Safetynet (ctsProfile: False). Tested with V16.4, V16.0 and V15.3. None of them passes the safetyNet. Have also tried installing the props module to no avail.
Google play store shows as uncertified (yet all the apps are available and install with no restrictions).
Battery charging light turns off when I turn the screen on and turns back on when the screen is off (Maybe it's intended to be like that, not sure)
What's working:
Pretty much everything other than what I wrote above it seems. The rom is very fast and stable, my phone feels considerably snappier than it did on stock Nougat and there doesn't seem to be many bugs at all. Only thing I've noticed is the battery life doesn't seem to be great but that could just be some installed apps or my phone. I haven't tested the dualsims yet but I will soon and I'll post the result here.
Testing Camera...
I'll continue updating the thread according to your feedback and my testing.
Click to expand...
Click to collapse
Sigh. First of all. Link is not allowed, delete it before we get trouble. Furthermore your guide isn't really helping anyone, since all information can be get in the other thread (nfound announced official oreo). You just snacked away Oki's guide and inserted a different ROM link. Tbf your information about magisk is fine and new, but that's it.
Cool, an easy guide to get you started.
Thanks man.
GabbaGandalf42 said:
Sigh. First of all. Link is not allowed, delete it before we get trouble. Furthermore your guide isn't really helping anyone, since all information can be get in the other thread (nfound announced official oreo). You just snacked away Oki's guide and inserted a different ROM link. Tbf your information about magisk is fine and new, but that's it.
Click to expand...
Click to collapse
I belive the link is allowed. A Forum mod said so on NFounds AEX thread.
I didn't snatch anything. I used guides that exist because they work and I gave props to every single person I could think of. I never claimed this was all my work. Just trying to help other people who want to try the ROM or are interested in how it performs.
I think the rom has something to do with CTS because it's a beta rom. It might not CTS approved. That's why magisk won't work. Similar to Android P DP.
https://developer.android.com/preview/release-notes
However, We can try to change or add ro.build.fingerprint in the build.prop file to the valid one. Not sure that it will work or not.
For example.
Code:
ro.build.fingerprint=ZTE/P996A04_N/ailsa_ii:7.0/NRD90M/20170215.164309:user/release-keys
Can /system be mounted as RW in this rom?
blackpac said:
Can /system be mounted as RW in this rom?
Click to expand...
Click to collapse
You can edit system just from TWRP.
mickey36736 said:
I think the rom has something to do with CTS because it's a beta rom. It might not CTS approved. That's why magisk won't work. Similar to Android P DP.
https://developer.android.com/preview/release-notes
However, We can try to change or add ro.build.fingerprint in the build.prop file to the valid one. Not sure that it will work or not.
For example.
Code:
ro.build.fingerprint=ZTE/P996A04_N/ailsa_ii:7.0/NRD90M/20170215.164309:user/release-keys
Click to expand...
Click to collapse
Didn't work unfortunately. Edited the ro.build.fingerprint and it still failed safetynet check.
SAFETYNET-FIX
Here you go : https://androidfilehost.com/?fid=674106145207489292
Fixes the safetynet - tested on 16.4 and 16.0
raystef66 said:
Here you go : https://androidfilehost.com/?fid=674106145207489292
Fixes the safetynet - tested on 16.4
Click to expand...
Click to collapse
Thank you, it works
all set up and running
Predatorhaze said:
all set up and running
Click to expand...
Click to collapse
How is battery life? Did you get substratum running? How is the sound without v4a and ainur. How is the sound with v4a+ainur?
battery dont know yet,but i dont use any sound mods on stock rom.Didnt try substratum.....i can try,but not gonna use it
GabbaGandalf42 said:
How is battery life? Did you get substratum running? How is the sound without v4a and ainur. How is the sound with v4a+ainur?
Click to expand...
Click to collapse
Accubattery says 5 hours SOT but I have only actually gotten 2. Again, this is probably a problem on my side and not the ROM. I need to check over the installed apps. Overall, actually better than 7.1.1 Nougat IMO since I was getting those bad results there too (Shouldn't have restored all the apps on first start).
Soundwise you shouldn't need anything. It's an official ROM and everything works properly. I haven't tested with any mods and I personally won't.
Victor13f said:
Accubattery says 5 hours SOT but I have only actually gotten 2. Again, this is probably a problem on my side and not the ROM. I need to check over the installed apps. Overall, actually better than 7.1.1 Nougat IMO since I was getting those bad results there too (Shouldn't have restored all the apps on first start).
Soundwise you shouldn't need anything. It's an official ROM and everything works properly. I haven't tested with any mods and I personally won't.
Click to expand...
Click to collapse
Battery doesn't sound too good. And personally I won't try it out until someone checked if substratum works. Cause if substratum works, I am able to enjoy the 'swift Black's theme, which boosts battery life by having real black everywhere. That means that the amoled screen will use less power. Also it's beautiful af and I don't want to miss it
Two questions please:
1. would flashing no-verity-opt-encrypt do anything for this ROM? as in, making encryption optional?
2. would it be a good idea to flash FASTBOOT_UNLOCK_EDL_N if I want to change my recovery now that I am no longer on N?
GabbaGandalf42 said:
Battery doesn't sound too good. And personally I won't try it out until someone checked if substratum works. Cause if substratum works, I am able to enjoy the 'swift Black's theme, which boosts battery life by having real black everywhere. That means that the amoled screen will use less power. Also it's beautiful af and I don't want to miss it
Click to expand...
Click to collapse
Substratum works, used swift black theme 8.0 pixel or nexus
GabbaGandalf42 said:
Battery doesn't sound too good. And personally I won't try it out until someone checked if substratum works. Cause if substratum works, I am able to enjoy the 'swift Black's theme, which boosts battery life by having real black everywhere. That means that the amoled screen will use less power. Also it's beautiful af and I don't want to miss it
Click to expand...
Click to collapse
Batterywise, I flashed the jojoc battery module and it's looking a lot better already
Here is working fine but how do I remove the operator name from the status bar?
Battery is absolutely horrible, coming from a beta tester. If you experience terrible battery it isn't a problem on your side, it's the beta rom. At best, I get barely 3 hours of screen on time only browsing Facebook
Hi !
I need help with Naptime (Francisco Franco).
The setting i've made under section "advanced->apps" resets every reboot to default values.
Unfortunatly It also resets by time whyle the phone ist running a bit (2-3h)
Phone is galaxy s4 9505 i've testet with lineage 15.1 and optimized lineage 16, rooted with magisk.
---please please please help---
can you send a screenshoots with this settings section?also have you installed magisk modules or xposed?
paranoic(d) said:
can you send a screenshoots with this settings section?also have you installed magisk modules or xposed?
Click to expand...
Click to collapse
Hmm,
I dont know how to insert a image in my Post... It's the last section of the advanced settings, that only appears if you got root. Called "Apps".
There are no xposed or magisk modules installed.
Best regards
hmm sorry i have never heard of it again.its the first time i have seen something like this.maybe trying to go back to stock and then root again?
hi there
i have unlocked bootloader and i can root my phone with magisk completely
but when i try to root with supersu , it flash completely in twrp but nothing appear in the app drawer and when i install apk it says phone is not rooted !
any one rooted mi a3 or any android one device with supersu ?
up up uppp
Why do you want to install root app which hasn't been updated for more than 2 years and pretty much no one uses it (at least with recent devices/Android versions)?
_mysiak_ said:
Why do you want to install root app which hasn't been updated for more than 2 years and pretty much no one uses it (at least with recent devices/Android versions)?
Click to expand...
Click to collapse
becauae when i flash magisk my phone start lagging and other problems ...
#MmdRza said:
becauae when i flash magisk my phone start lagging and other problems ...
Click to expand...
Click to collapse
Not sure how could be that related to Magisk, there are probably thousands of Magisk users with A3 phone and so far no one reported such issue. Personally I see no lagging or "other" problems while using Magisk. In each case, it would be better to invest your time to troubleshooting Magisk, where you have a high chance of finding a solution and possibly receiving a fix from developer (if your issue is valid). With SuperSU you're on your own.
SuperSU is very outdate
It´s a Crazy idea to install SuperSU in 2020, Magisk is more, more, and more better.
Hi.
Well, I have faced the same problem: flash magisk and... soft brick ?. I followed this tutorial https://magisk.me/root-xiaomi-mi-a3/ and
I tried 2 times and doesn't work, so I went back to stock room.
Please somebody could help to solve. Thanks and sorry my bad english, I speak Portuguese...
the tutorial posted in the link above uses a specific boot.img (V10.3.5.0.PFQEUXM) are you sure you are using the correct rom to match the tutorial ?
instead why not use TWRP and root from there by flashing Magisk.zip over a clean Flash of the rom of your choice..?
i have used Magisk on my A3 with many different roms , no lagging issues atall , so i cannot suggest supersu as im not even sure it possible with the A3...
_mysiak_ said:
Not sure how could be that related to Magisk, there are probably thousands of Magisk users with A3 phone and so far no one reported such issue. Personally I see no lagging or "other" problems while using Magisk. In each case, it would be better to invest your time to troubleshooting Magisk, where you have a high chance of finding a solution and possibly receiving a fix from developer (if your issue is valid). With SuperSU you're on your own.
Click to expand...
Click to collapse
I recently installed magisk and my battery drain increases too much. I had to uninstall and flash stock rom
krishna.telgave said:
I recently installed magisk and my battery drain increases too much. I had to uninstall and flash stock rom
Click to expand...
Click to collapse
Can't confirm this, I have Magisk on all my phones and it doesn't cause any "battery drain". What was your screen off battery consumption with and without Magisk? I see no difference if I have Magisk installed or not.