something seems wrong in Magisk-v7 unpack/repack method. its making my device do bootloop at bootlogo. inspecting new-boot.img seems to me the size is smaller than its used to in Magisk-V6 and i am not able to unpack it with any boot repack/unpack tool.
ok. did some test.
dm-0 points to /data (i had storage encrypted)
if i move an app to sdcard, this app is mapped to dm-1 then the app patch in /mnt/asec
so more moved apps should create more dm-n paths?
Paget96 - small update regarding my last post about FC when using Ram Manager in beta 19. it seems that the issue was resolved. i completely uninstalled LSPEED, rebooted phone, reinstall LSPEED(i saved apk after i updated to beta19) and it seems to work now. dont know why it did that the 1st...
Paget96 latest beta 19 causes force close when choosing Ram Manager, this is suppose to be fixed on this version right? was using beta 17 and it does not have this issue. already rebooted and reset the app and settings.
E/AndroidRuntime( 8878): FATAL EXCEPTION: main
my stock firmware comes with Permissive sepolicy, how can i retain everytime device boots? my unit behaves differently when it is set to Enforcing-including Pokemon GO not connecting to server.
i already have solved this, but using manual method which means manually running readback on preloader.bin's actual address and region then again manually edit the resulting file for it to be flashable in spflashtools(u cannot directly use it)
thanks for update. tested with D and DLite both version works fine. stock Android 5.1 Kernel 3.10.72 here. one suggestion though, maybe a bit adjustment on treble knob, seems to have no effect---but it could be just my earphones though.